Feature Overview (aka. Goal Summary)

Standardize authentication providers tests

Goals (aka. expected user outcomes)

Make sure that all the authentication providers tests are automated and run periodically. 

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

<enter general Feature acceptance here>

Out of Scope (Optional)

High-level list of items that are out of scope.

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.