Comprehensive Test Plan: Divide Existing Cypress Test Suite into Separate Test Runs

[keisterj-oddball]

User Story or Problem Statement

As a member of the CMS Team, I want the ability to run a more focused set of E2E tests at various stages of the CMS deployment pipeline, so that I get faster testing feedback on core functionality of the CMS and improve the speed of our deployment pipeline.

Description or Additional Context

In order to create separate test runs for "Critical Path" and "Regression" tests, all existing cypress tests must be categorized as "Critical" or "Regression".

Steps for Implementation

1. Discuss existing cypress tests with the sitewide teams to determine priority of tests
2. Annotate existing cypress tests to be included in the appropriate test run(s)
3. Determine if any test reporting changes are required for new test runs
4. Create new workflow(s) for triggering specific test runs
5. Determine the appropriate placement of respective test runs within the CMS deployment pipeline (implementation can be done in a separate issue)

Acceptance Criteria

• All cypress tests should be annotated as "Critical" or "Regression"
• Independent "Critical Path" and "Regression" test runs should be able to be triggered
• There should be consensus regarding the placement of "Critical Path" and "Regression" test runs within the CMS deployment pipeline
• Verify test reporting is still in tact with the creation of separate test runs