Testing & QA

Unit tests, integration tests, E2E, QA, validation, and test automation

skills in category: 31,457
pages available: 1,311

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse testing & qa skills

Showing 4,249–4,272 of 31,457 skills

SnapAUse when you just want screenshots of every screen saved as image files — capture all screens/states/variants of a locally runnable app, no QA analysis, no findings, just the pictures. Triggers on "스크린샷 다 찍어줘", "모든 화면 캡쳐해서 저장", "capture all screens", "screenshot everything".testingVotes: 0GitHub stars: 2
ScriptifyAUse when asked to turn a QA or capture flow into a reusable static shell script so it can be re-run without an agent — generate a repo-native `.sh` that launches, seeds, and captures screenshots/video deterministically. Triggers on "정적 스크립트로 만들어줘", "sh 파일로", "에이전트 없이 재실행", "capture script 생성".testingshellbashVotes: 0GitHub stars: 2
ReproAUse when you want a video that reproduces a flow or an error/bug and saves the clip — a shareable recording of the steps that trigger a problem. Triggers on "오류 영상으로 남겨줘", "버그 재현 영상", "record a repro video", "capture a video of this bug".testingshellVotes: 0GitHub stars: 2
PreflightAUse when starting any app QA or test run, to check whether a repo can be run and tested locally — detect project type, verify the toolchain, discover how it runs and where screenshots/media should go — before capturing or testing. Triggers on "테스트 가능한 환경인지", "환경 점검", "preflight", "can I run this locally".testingrustgoVotes: 0GitHub stars: 2
CasewrightAUse when asked to generate or write automated test cases for a locally runnable app — turn user flows, routes, or QA findings into reusable tests (e2e, integration, unit, regression) in the repo's own test framework. Triggers on "테스트 케이스 만들어줘", "테스트 작성", "회귀 테스트", "generate tests", "write test cases", "e2e 테스트 생성".testinggotestingVotes: 0GitHub stars: 2
BugsweepAUse when asked to QA an app end to end, run a full-path / 전체 경로 / 전수 QA, capture screenshots of every screen, or verify all user flows (signup, login, every feature) of a locally runnable web, iOS, Android, API, or monorepo project. Triggers on "전수 QA", "모든 화면 캡쳐", "직접 써보고 버그 찾아줘", "full QA pass".testinggoapiVotes: 0GitHub stars: 2
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
BreachsweepAUse when asked to security-test, pentest, or find vulnerabilities in a locally runnable app you own — auth/authorization (IDOR), input validation (injection), secret exposure, security headers, insecure cookies/CORS. Triggers on "보안 점검", "취약점 찾아줘", "security audit", "pentest my app".testinggosqlVotes: 0GitHub stars: 2
Flutter TestingADesign, write, or review Flutter unit, widget, golden, and integration tests. Use for test strategy, regressions, fakes, async UI behavior, and end-to-end flows; use device testing for operational emulator or hardware control.testinggotestingVotes: 0GitHub stars: 7
Qa ExpertAYou are a quality assurance specialist with expertise in test automation, testing strategies, and quality processes. You design and implement comprehensive testing that catches bugs before production.testingtypescriptgoVotes: 0GitHub stars: 2
crud-stackDBuild or extend a multi-tenant, role-scoped, audited web app on a generic-CRUD architecture — Express + Sequelize behind one crudThat factory with per-model controller hooks, a no-build-step vanilla JS frontend, a shared rules module both sides run, and a three-container Docker/Traefik/MySQL deployment. Use when starting a new project of this shape, or when adding a model, controller, route, view, test or environment variable to one. Covers the CRUD factory and its hooks, the access model, pr...testingjavascriptrustVotes: 0GitHub stars: 3
TestingAThis skill should be used whenever writing, reviewing, or fixing tests — when the user asks to "write tests", "add tests for X", "test this function/class", "improve test coverage", "review my tests", "why is this test flaky", "should I mock this", "how do I test X", mentions TDD or characterization tests, asks how to test code that has no tests or seems untestable, or when Claude has just written production code and is about to add tests for it. Provides test-design fundamentals, a test-doub...testingtypescriptpythonVotes: 0GitHub stars: 2
Test PlanningAUse when turning a behavior specification and codebase recon into an approved test plan — choosing test cases and coverage depth per behavior, picking the right scope (unit, integration, contract, schema, property, UI, E2E), justifying every choice, running an adversarial critique of the plan, and reviewing it with the user before any test is written. Invoked by /test-write between extraction and authoring.testinggotestingVotes: 0GitHub stars: 2
Test AuditingAUse when assessing a whole repository's test suite rather than specific test files — finding where protection is weakest, diagnosing systemic problems across the suite, ranking modules by risk against the strength of their tests, and producing a map that says where to spend test effort next. Invoked by /test-audit. For per-test defects in a known set of files, use /test-review instead.testinggotestingVotes: 0GitHub stars: 2
Spec Test VerificationAUse when auditing written tests back against the behavior specification and test plan that produced them — checking traceability in both directions, running the full suite, classifying every failure as a spec/code mismatch versus a test defect versus an environment problem, and reporting which described behaviors appear unimplemented. Invoked by /test-write as the final phase.testinggogitVotes: 0GitHub stars: 2
Behavior ExtractionAUse when turning a described behavior — a JIRA ticket, a GitHub PR or issue, a spec document, or free-form text — into a structured, testable behavior specification before any test is planned or written. Produces numbered behaviors in Given/When/Then anchored to quotes from the source, plus an explicit register of what the description leaves unspecified. Invoked by /test-write; also useful on its own when acceptance criteria need to be pinned down before work starts.testingrustgoVotes: 0GitHub stars: 2
Commit CompositionAUse when turning a dirty working tree into a sequence of atomic commits — surveying what changed, grouping hunks by intent rather than by file, screening for secrets and contamination, verifying each prospective commit builds on its own, and creating the commits after user approval. Invoked by /git-workflow:commit; also useful directly when a session has produced several unrelated changes that should not land as one commit.testinggobashVotes: 0GitHub stars: 2
Step ExecutionAUse when running an approved step plan against a live system — spawning agentic-qa:step-executor to drive the browser, API, and CLI. Governs the four verdicts (pass/fail/blocked/skipped), which evidence is required by surface, the choice between the claude-in-chrome and playwright browser drivers, the backoff retry policy for environment failures, the irreversible-step check, and the rule against adapting an action to force a pass. Invoked by /agentic-qa:walkthrough after the User Gate, along...testinggobashVotes: 0GitHub stars: 2
Review AuthoringAUse when turning journal entries into a finished career document — a performance self-assessment, a promotion packet, resume or LinkedIn bullets, or a weekly rollup — by clustering entries into themes, mapping them to the reader's framework, drafting in the user's voice, and verifying that every claim and every number traces back to a dated entry. Invoked by /accomplishments:review.testingrustgoVotes: 0GitHub stars: 2
Playwright Visual RegressionACreate and maintain visual regression tests, what to screenshot, how to stabilize state first, threshold selection, masking third-party noise, and baseline management. Use when adding VR coverage or diagnosing a flaky screenshot.testingtypescriptrustVotes: 0GitHub stars: 8
Playwright Pageobject TestingACoding standard for tests and page objects in this repository, locator priority, page object structure, fixtures, assertions, and the anti-patterns that get a change rejected. Use before writing or reviewing any test code.testingtypescriptgoVotes: 0GitHub stars: 8
Playwright McpADrive the live application through Playwright's MCP servers for exploration, locator discovery, test generation, and failure diagnosis. Use when planning coverage, confirming an accessible name, generating a case, or investigating a failure.testinggogitVotes: 0GitHub stars: 8
Accessibility CheckerAValidate WCAG 2.1 Level AA compliance and accessibility best practices.testingtypescriptgoVotes: 0GitHub stars: 666
Xray CliCXray Cloud test management via `bun xray` CLI: create/list tests, manage test executions and plans, import JUnit/Cucumber/Xray JSON results, update run statuses, back up and restore projects, link defects. Triggers on: create a test in Xray, import test results to Xray, list Xray executions, update run status, backup Xray project, restore Xray tests, link defect to run, sync tests, Xray auth login. Do NOT use for: writing automated tests (test-automation); documenting test cases or ROI analys...testinggobashVotes: 0GitHub stars: 26
Test DocumentationAAnalyze, prioritize, and document test cases in TMS (Jira/Xray), or repair an existing Story-ATS-ATP-ATR-TC cascade through a sealed explicit mode. Use for Test/ATP/ATR artifacts, ROI and automation verdicts, maintaining traceability, fix-traceability, or broken TMS links. The repair-traceability mode audits, plans, waits for explicit approval, applies, and verifies without launching the general documentation workflow. Do NOT use for writing test code (test-automation) or running suites (regr...testinggoc#Votes: 0GitHub stars: 26