github-actions

Playwright on GitHub Actions

Examples demonstrating how to run Playwright tests on GitHub Actions with Currents.

Examples

Example	Description	Folder
Basic Setup	Standard CI setup with sharding and reporting	setup-ci/
Orchestration	Optimized parallel execution with load balancing	orchestration/
Rerun Failed	Workflow to rerun only failed tests from previous build	rerun-failed/
Visual Testing	Integration with Argos for visual regression testing	argos/

Prerequisites

1. Currents Account: Get your Record Key and Project ID from Currents Dashboard.
2. GitHub Secrets: Set CURRENTS_RECORD_KEY in your repository secrets.
3. Project ID: Update the workflows or environment variables with your Project ID (or use CURRENTS_PROJECT_ID secret).

Directory Structure

• .github/workflows/: Contains all the YAML workflow files.
• setup-ci/: Basic test suite and configuration.
• orchestration/: Configuration for orchestration.
• rerun-failed/: Documentation for rerun workflows.
• argos/: Dedicated test suite for visual testing.

Results

The results are being reported to Currents for more efficient troubleshooting, and monitoring test suite flakiness and performance.

Currents will collect the following information:

• console output
• screenshots
• videos
• trace files
• timing
• outcomes
• flaky tests
• error details
• tags for more convenient management of the tests

Currents Dashboard Results

Here's how the results are being displayed in Currents dashboard.

gh-actions-demo.mp4

PR Comment and Git Commit Status

Currents will add inline information to GitHub Pull Request.

• a comment containing run results summary

• git commit status check for each detected project

Additional Resources

• Playwright Features on Currents
• Integration Documentation
• CI Build ID Guide