Pension | Make E2E Tests Concurrent

[ToddWebDev]

Pension | Make E2E Tests Concurrent

Description

To improve the efficiency of our CI/CD pipeline, the end-to-end (E2E) tests for the Pension Benefits form need to be updated to support concurrent execution. Currently, multiple test suites are grouped into a single file, which prevents them from being run concurrently. This task involves separating each test suite into its own file, allowing the Platform team to configure the tests to run concurrently within the pipeline.

Tasks

• Analyze the current E2E test file structure and identify test suites that can be separated.
• Refactor the E2E tests, ensuring each suite resides in its own file.
• Ensure that test files follow naming conventions and are well-organized for maintainability.
• Confirm that each test suite runs independently without dependencies on other tests.
• Run tests locally to verify no regressions or failures after the separation.
• Document changes in the appropriate project documentation.

Acceptance Criteria

• [ ] Each test suite is moved into its own individual file.
• [ ] All E2E tests are confirmed to run successfully and independently.
• [ ] Tests are validated to run concurrently in local environments without interference.
• [ ] Platform team is notified that tests are ready for concurrent execution in the CI/CD pipeline.
• [ ] Changes are documented and communicated to the team.

Definition of Done

• The E2E tests are separated into independent files.
• Tests run successfully in local environments without regressions.
• The Platform team confirms that tests can be executed concurrently in the CI/CD pipeline.
• All related documentation is updated to reflect the new test structure.