bcgov / bcgov/cas-reporting

Use Nx Atomizer to split E2E testing into chunks

Open
#241 3 comments 0 reactions 0 assignees View on GitHub
DevOps Task
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## Description:

_e2e tests currently work, but could they work **better?_** This ticket aims to address that question. We should be able to use Nx Atomizer, an _automatic_ e2e test splitter. It breaks e2e runs into smaller pieces, allowing for CI to be rerun on any flaky tests or identify any errors faster.

## Dev story:

_I want_ to use Nx Atomizer
_because_ it will automatically split E2E tests
_and this will help me to_ allow for easier identification/reruns of flaky tests and allow for parallelization.

## Development Checklist and tasks:

- [ ] Identify configuration for E2E tests as they are currently.
- [ ] Recreate exact E2E test run environment with NX.
- [ ] Use Nx config to allow for automatic test splitting.
- [ ] Set GitHub Actions to run using split tests.

## Consideration and notes

- [Atomizer general docs](https://nx.dev/ci/features/split-e2e-tasks)
- [Playwright manual config](https://nx.dev/nx-api/playwright#nxplaywright-configuration)

## **Definition of Ready** (Note: If any of these points are not applicable, mark N/A)

- [ ] ~~User story is included~~
- [ ] ~~User role and type are identified~~
- [ ] Acceptance criteria are included
- [ ] ~~Wireframes are included (if required)~~
- [ ] Design / Solution is accepted by Product Owner
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

## **Definition of Done** (Note: If any of these points are not applicable, mark N/A)

- [ ] Acceptance criteria are tested by the CI pipeline
- [ ] UI meets accessibility requirements
- [ ] Configuration changes are documented, documentation and designs are updated
- [ ] Passes code peer-review
- [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
- [ ] Ticket is ready to be merged to main branch
- [ ] Can be demoed in Sprint Review
- [ ] Bugs or future work cards are identified and created
- [ ] Reviewed and approved by Product Owner

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by identifying the current E2E test configuration and the GitHub Actions workflow that runs it, then read the linked Nx Atomizer documentation. Done means the existing E2E environment is reproduced with Nx, tests are automatically split, and CI runs the split tasks with flaky-test reruns or parallelization supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, playwright
Domain
ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.