QA Standards - Ask VA Integration - Ask VA

[it-harrison]

General Information

VFS team name

Ask VA Integration

VFS product name

Ask VA

VFS feature name

Ask VA

Point of Contact/Reviewers

@it-harrison - Ian Harrison - QA

---

QA Standards

Note: all standards are launch-bocking.

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):

E2E Test Participation

• Standard has been met
• Standard has not been met

Explanation of failure to meet standard (if applicable):

Unit Test Coverage

• Lines %: 82.81

• Functions %: 74.81

• Statements %: 82.21

• Branches %: 71.35

• Standard has been met

• Standard has not been met

Explanation of failure to meet standard (if applicable):

All categories must have at least 80% coverage.

Endpoint Monitoring (Completed Playbook)

• Standard has been met
• Standard has not been met

Explanation of failure to meet standard (if applicable):

Logging Silent Failures

• Standard has been met
• Standard has not been met

Explanation of failure to meet standard (if applicable):

---

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