Use Case

As a driver developer writing tests
I want a metadata filter for auth, could use the serverless model of forbid/allow/require
So that we have a more consistent approach to filtering tests based on environmental settings

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Unknowns

• questions that need to be answered to determine implementation

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc