Open
Description
General Information
VFS team name
Identity
VFS product name
sign-in transition
VFS feature name
interstitial
Point of Contact/Reviewers
@it-harrison - Ian Harrison - QA
QA Standards
Regression Test Plan
- Standard has been met
- Standard has not been met
Explanation of failure to meet standard (if applicable):
Test Plan
- Standard has been met
- Standard has not been met
Explanation of failure to meet standard (if applicable):
Traceability Reports
- Standard has been met
- Standard has not been met
Explanation of failure to meet standard (if applicable):
No traceability reports included
E2E Test Participation
- Standard has been met
- Standard has not been met
Explanation of failure to meet standard (if applicable):
Unit Test Coverage
-
Lines %: 91.67
-
Functions %: 90.00
-
Statements %: 91.67
-
Branches %: 96.15
-
Standard has been met
-
Standard has not been met
Explanation of failure to meet standard (if applicable):
Endpoint Monitoring (Completed Playbook)
- Standard has been met
- Standard has not been met
Explanation of failure to meet standard (if applicable):
A link to DataDog is provided but by itself this does not satisfy the playbook requirement.
Logging Silent Failures
- Standard has been met
- Standard has not been met
Explanation of failure to meet standard (if applicable):
No logging silent failures artifact included
Next Steps for the VFS team
- Questions? For the most timely response, comment on Slack in your team channel tagging
@platform-governance-team-members
with any questions or to get help validating the issue. - Close the ticket when your Product Owner determines that you have sufficiently met the QA Standards.
Platform directions
- Update "Issue Title" to be of the form "QA Standards - VFS Team - VFS Product"
- Add the VFS team, product name, and feature name
- Add your name, practice area, and GH handle under Point of Contact/Reviewers
- Complete the QA Standards section, making sure to include an "Explanation of failure to meet standard" for every Standard the product does not meet.
- Link to the Collaboration Cycle Request epic
- Add epic's milestone
- Add assignees:
- VFS PM
- Yourself (optional)
- Add labels:
- VFS team label
- VFS product label
- QA-standards label
- launch-blocking label if the product has failed to meet a required QA Standard
Activity