playwright-regression-testing
/playwright-regression-testing
Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.
- Author
- fugazi ↗
- Repository
- test-automation-skills-agents ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 8
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.
Original author description
Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.
How it works
- When to Use This Skill
- Prerequisites
- Quick Reference
- Red Flags
- References
- Verification
SKILL.md preview
--- name: playwright-regression-testing description: 'Govern Playwright TypeScript regression suites across many tests. Use when asked to plan, select, tier, execute, or optimize suites with risk/change analysis, tags, CI/CD, sharding, flaky-test management, or suite-health metrics; not for authoring one UI spec. Keywords: regression strategy, smoke tests, test selection, CI pipeline, flaky tests, test sharding, impact analysis, git diff.' license: 'Complete terms in LICENSE.txt' --- # Playwright Regression Testing (TypeScript) Strategy and best practices for automated regression testing of web applications using Playwright with TypeScript. > **Activation:** This skill is triggered when working with regression test strategy, test suite selection, test prioritization, CI/CD pipeline testing, flaky test management, test sharding, or optimizing test execution for web applications using Playwright. ## When to Use This Skill - **Plan regression suites** with risk-based and change-based test selection - **Organize tests** into tiers (smoke, sanity, selective, full regression) - **Optimize execution** with parallelization, sharding, and time-budget strategies - **Integrate with CI/CD** using GitHub Actions pipelines - **Manage flaky tests** with quarantine, retry policies, and root cause tracking - **Monitor suite health** with execution time, flake rate, and detection metrics - **Select tests after changes** using git diff analysis and impact mapping ### Do NOT Use For - Authoring a single UI spec or page-object model (use `playwright-e2e-testing`). - Driving a live browser interactively for debugging (use `playwright-cli`). - Selenium/Java regression suites (use `webapp-selenium-testing`). - API contract testing in isolation (use `api-testing`). ## Prerequisites | Requirement | Details | | -------------- | ---------------------------------------- | | Node.js | v18+ recommended | | Playwright | `@playwright/test` package | | TypeScript | `typescript` configured in project | | Browsers | Installed via `npx playwright install` | | Git | Required for change-based test selection | | GitHub Actions | Recommended CI/CD platform | --- ## Quick Reference **Tiers:** Smoke (<2min, every commit) → Sanity (<10min, every PR) → Selective (<30min, on merge) → Full (<60min, nightly/pre-release). **Key tags:** `@smoke`, `@sanity`, `@regression`, `@e2e`, `@api`, `@destructive` — exactly one per test, never on `describe()` blocks. Domain-specific extensions (e.g., `@a11y` in accessibility skills) are allowed alongside, but only one execution tag per test. **CLI:** `npx playwright test --grep @smoke` | `--grep @regression` | `--grep-invert @destructive` | `--shard=1/4` | `--last-failed` For full tier model, regression types table, and tag taxonomy, see [`references/regression-catalogs.md`](references/regression-catalogs.md). --- ## Red Flags - Treating flaky tests as "fixed" by adding retries or `waitForTimeout` — quarantine and root-cause instead. - Running the full suite on every commit — use tiered selection (smoke on commit, full nightly). - Quarantining tests silently with no tracking ticket — quarantine must be temporary and owned. - No change-based selection — running everything regardless of what changed wastes CI budget. - Ignoring suite-health metrics (rising duration, climbing flake rate) until they block releases. --- ## References | Document | Content | | ----------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | [Regression Strategy](./references/regression-strategy.md) | Tier model (smoke→full), regression types, triggers, directory layout, test tagging and tag taxonomy | | [Regression Selection](./references/regression-selection.md) | Test selection (change-based, risk-based, historical, time-budget) and test naming conventions | | [Regression Best Practices](./references/regression-best-practices.md) | Locator priority, web-first assertions, test independence, `test.step()` reporting, complete worked example test | | [CI/CD Integration](./references/ci-cd-integration.md) | GitHub Actions tiered pipeline, sharding, merge reports, Playwright config, performance optimization, CLI reference | | [Flaky Management](./references/flaky-management.md) | Retry policies, quarantine strategies, detection checklist, suite health metrics, troubleshooting | --- ## Verification - [ ] **Smoke test subset identified** — Tagged `@smoke` tests run in under 2 minutes - [ ] **No test duplication** — Each scenario tested exactly once at the appropriate level - [ ] **Test isolation verified** — Running tests in random order produces same results as sequential - [ ] **Flaky test baseline established** — All tests pass 5/5 consecutive runs
Files in this package (8)
- LICENSE.txt 1 KB
- SKILL.md 5 KB
- references/ci-cd-integration.md 8 KB
- references/flaky-management.md 4 KB
- references/regression-best-practices.md 5 KB
- references/regression-catalogs.md 2 KB
- references/regression-selection.md 4 KB
- references/regression-strategy.md 6 KB
Versions
The database has no other skills named playwright-regression-testing.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 3cd5ca129513 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95qa-e2e-playwright
Use this skill when the user says 'playwright', 'playwright test', 'playwright config', 'locators', 'storageState', 'trace viewer', 'playwright codegen', 'playwright sharding', 'playwright fixtures'. It writes and structures Playwright Test suites in TypeScript: config,… - 85proof
QA and testing engineer — test strategy, E2E suites, API tests, flaky test triage, coverage. Use when asked to "write E2E tests", "design a test strategy", "triage flaky tests", or "check test coverage". - 90quality-regression-testing
Use when the user asks about regression testing, test selection, regression suite design, automation maintenance, flaky tests, or regression metrics. Do NOT use for: smoke/BVT testing (quality-smoke-testing), acceptance testing (quality-acceptance-testing), or exploratory… - 100v1-e2e-testing
Use when implementing or debugging browser end-to-end tests, especially Playwright or flaky tests. Triggers on "E2E test", "Playwright", or "flaky browser test". - 100e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI. - 100qe-test-execution
Orchestrates test suite execution with parallel sharding, intelligent retry, and real-time reporting across Jest, Vitest, and Playwright. Use when running test suites, optimizing execution time, handling flaky tests, configuring CI test pipelines, or analyzing test run results.