GitHub Action Playwright Flaky Test Analyzer
A GitHub Action that finds and analyzes unreliable Playwright tests, identifies which browsers cause inconsistent pass or fail results, and helps teams fix…
Platform availability
Available on 0 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
8/100 Low
- Maintained
- 0GitHub repository no longer exists
- Popular
- No data
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- No data
Based on 2 of 4 factors.
No GitHub repository data collected yet.
Checked 54 days ago - source: GitHub (agentcatalog/github-action-playwright-flaky-test-analyzer)
Resources & Compatibility
Requirements not published yet.
Checked 23 days ago - source: Docker Hub image tags and published docs
First-install notes
- Check out the repo first In your workflow file, add a checkout step before the analyzer so the job has your code and Playwright test reports. Without this, the action has no test results to look at. source
- Install the test dependencies too If your Playwright tests need extra packages, add a setup and install step for the programming language your project uses before the test run. Missing packages can fail the tests, which leaves the analyzer nothing useful to read. source
- Set up a self-hosted runner If you use your own computer or server to run GitHub Actions jobs, install the self-hosted runner service with sudo ./svc.sh install on Linux. Stop the runner first if it is running, because an active runner can block proper service setup. source
Fetched 2 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How can I run the Playwright Flaky Test Analyzer on a new machine?
The execution guide covers running the analyzer on any machine, including a fresh clone or daily use.
What should I inspect in the application when a Playwright test is inconsistent?
Inspect the application, run the browser with 3g throttle, and look for the element that loads last.
Which types of flakiness should I investigate in GitHub Actions?
Check timing issues, shared state, external dependencies, and environment drift.
What robustness goal is mentioned for super intermittent Playwright flake?
The goal is to prove the robustness of a test before it makes it into master.
Answers sourced from github.com, www.kleore.com, www.reddit.com, www.reddit.com
Community
Collected 49 days ago - public community threads