Visual Testing

petrkindlmann/qa-skills/skills/visual-testing

by petrkindlmannb3bb61bd268bMIT168 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 4 months ago

Implement visual regression testing with Playwright screenshots, Chromatic, Percy, and Argos CI. Covers baseline management, diff threshold tuning, dynamic content masking, responsive viewport testing, and review/approval workflows. Use when: "visual test," "screenshot," "visual regression," "pixel diff," "snapshot diff," "update baselines," "Chromatic," "percy snapshot," "argos screenshot." Not for: bulk baseline regeneration after a redesign broke many tests — use selector-drift-recovery; cross-browser rendering matrices — use cross-browser-testing; general Playwright test structure — use playwright-automation. Related: playwright-automation, ci-cd-integration, cross-browser-testing.

Instructions onlySoftware Development

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
references/recipes.md6.3 KBtext/markdown
SKILL.md17.5 KBtext/markdown

Source and attribution

Source:petrkindlmann/qa-skillsinskills/visual-testingat commitb3bb61b

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from petrkindlmann/qa-skills

Unit Testing

petrkindlmann

Guides writing effective unit tests in Jest, Vitest and pytest, covering test doubles, coverage gating, snapshots, fake timers and mutation testing.

Software Development168updated 4 months ago

Test Suite Curation

petrkindlmann

Audit a whole regression suite and prune/restructure it with evidence: per-test coverage fingerprinting, AST near-duplicate clustering, CI-history mining for never-failing and flaky tests, prune decision rules (redundant/obsolete/low-value/keep), smoke/core/extended tiering by risk and defect-detection history, and a defensible "what we deleted and why" record. Deletion is destructive — quarantine and human sign-off are mandatory. Use when: "audit the test suite," "prune redundant tests," "find duplicate tests," "which tests can we delete," "restructure into smoke/core/extended," "is this test pulling its weight," "shrink the regression suite." Not for: Judging whether an individual test is WELL-WRITTEN (smells, assertions) — that is ai-qa-review. Healing one flaky test at runtime — that is test-reliability. Bulk selector regeneration after a UI refactor — that is selector-drift-recovery. Related: ai-qa-review, coverage-analysis, test-reliability, risk-based-testing, qa-project-context.

Awaiting classification168updated 4 months ago

Test Strategy

petrkindlmann

Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.

Awaiting classification168updated 4 months ago

Test Planning

petrkindlmann

Builds a one-page sprint or release test plan with coverage mapping, effort estimation, prioritization, allocation, and scheduling.

Productivity & Workflow168updated 4 months ago

Test Migration

petrkindlmann

Guides incremental test-suite migration between frameworks, such as Selenium, Cypress, or Jest to Playwright or Vitest, with parallel CI.

Software Development168updated 4 months ago

Test Data Management

petrkindlmann

Guides creation, seeding, anonymization and cleanup of deterministic, isolated test data using factories, fixtures and synthetic generation.

Software Development168updated 4 months ago