Currents collects Playwright test results from GitHub Action CI Runners, together with the generated artifacts (trace files, screenshots, videos) for more efficient troubleshooting and providing insights into the test suite performance:
console output
screenshots
videos
traces
Playwright in GitHub Actions
and speed up you CI pipeline by running tests in parallel - playwright support splitting the tests between multiple CI machines using --shard CLI flag.
Read our CI Optimization guide to discover how to speed up your Playwright test in GitHub Actions.
Example
The showcases running Playwright tests in GitHub Actions. We've included several config files to exemplify the workflows:
- run Playwright tests in parallel using 3 shards of GitHub Actions Matrix and pwc command.
- run Playwright tests in parallel run using 3 shards of GitHub Actions Matrix and configuring Currents Reporter in playwright.config.ts.
- run Playwright tests in parallel Playwright using Orchestration Setup and GitHub Actions Matrix. Currents Orchestration speeds up CI runs by up to 40% (compared to native sharding) by optimally balancing tests between the available machines.
- run Playwright tests in parallel using Currents Orchestration, use Argos CI for visual testing.
Re-run only failed tests in GitHub Actions
When a workflow fails in GitHub Actions you have the option to re-run the failed jobs. However, an additional setup is required for properly configure Playwright for rerunning only the failed tests.
If you're using Currents Orchestration for running your Playwright tests you can also fetch the results of from API.
Currents Orchestration dynamically assigns tests to all the available CI runners, that's why you should select Re-run all jobs when using Currents Orchestration. Read more at Re-run Only Failed Tests guide.
