VFS teams will be evaluated as to whether or not they are meeting these standards at the Collaboration Cycle Staging Review.

Please note: These standards will likely evolve over time as tooling evolves and processes mature.

Standard area

ID

Standard description

Severity

Regression Test Plan

QA1

Product must have a regression test plan that verifies the product changes do not cause previously integrated functionality to break.

Warning, not launch-blocking

Test Plan

QA2

Product must have a test plan that describes the method by which changes to the product will be verified.

Warning, not launch-blocking

Traceability Reports

QA3

Product must have a Coverage for References report that demonstrates user stories have been verified by test cases in the test plan. Product must also have a Summary (Defects) report that demonstrates defects discovered during QA testing were discovered by executing tests.

Warning, not launch-blocking

E2E Test Participation

QA4

Product must have 1 or more E2E tests.

Launch-blocking

Unit Test Coverage

QA5

Product must have 75% or higher unit test coverage.

Warning, not launch-blocking

How standards are validated

Please note that you will need access to TestRail in order to access many of these artifacts. See Quality assurance artifacts for more information.

Regression Test Plan

VFS teams can create a Regression Test Plan under the Test Runs & Results tab of TestRail. For an example regression plan, see the VSP-Facility Locator regression plan. VFS Teams not using TestRail are still expected to share a Regression Test Plan at the Collaboration Cycle Staging Review.

Test Plan

VFS teams can create a Test Plan under the Test Runs & Results tab of TestRail. For an example regression plan, see the Cross-Browser Search test plan. VFS Teams not using TestRail are still expected to share a Test Plan at the Collaboration Cycle Staging Review.

Traceability Reports

VFS teams can create a Traceability Report by clicking on the appropriate link in the Create Report panel on the Reports tab of TestRail. For an example of a Coverage for References report, see this Coverage Report for Search. For an example of a Summary (Defects) report, see this Summary (Defects) report for Search. VFS Teams not using TestRail are still expected to share Traceability Reports at the Collaboration Cycle Staging Review.

E2E Test Participation

Create at least one Cypress test spec in a tests/e2e folder in your product directory that follows the conventions described in the Writing an end-to-end test document. See End-to-end testing with Cypress for more information about writing Cypress tests on the platform.

Unit Test Coverage

Visit the Unit Test Coverage Report of the Frontend Dashboard and find your product in the table. If your product is not yet listed, you can generate the code coverage report locally by running the following command within vets-website: yarn test:coverage-apps.