Automated testing in CircleCI
Because QAShift tests are standard Playwright, they run as an ordinary CircleCI job, split across parallel containers, with artifacts for every failure.
CircleCI is built for fast, parallel pipelines, which suits end-to-end suites well. QAShift supplies the suite: generated, maintained and verified tests for your critical journeys.
There is no proprietary runner. The tests run with the same Playwright tooling as any other project.
How it works with CircleCI
- 1
Generate tests
QAShift writes Playwright tests and commits them to your repository.
- 2
Add a job
A CircleCI job installs Playwright browsers and runs the suite.
- 3
Split for speed
Use CircleCI parallelism to shard the suite across containers.
- 4
Store artifacts
Traces, videos and reports are stored as job artifacts.
What you get
- Standard Playwright, no custom orb required
- Sharding across parallel containers
- Artifacts for every failure
- No per-run fees from QAShift
Frequently asked questions
Are runs in CircleCI limited?
No. Tests run on your own CircleCI runners, so runs are unlimited on every QAShift plan, including Free.
Do the tests need a special runner or plugin?
No. Tests are standard Playwright, so they run with the usual Node and Playwright setup used by any project.
Can failures block a merge?
Yes. The test job reports a status check, and on paid plans flaky failures are classified so only verified failures block.
Ship without fear.
Start testing free in minutes, or let a QAShift engineer deliver your first morning report within 5 days.