Testing & QA skills for Codex
Skills for tests that catch real bugs and stay green for the right reasons: unit test design, Vitest, Jest, pytest, Go and JUnit suites, Playwright and Cypress end-to-end tests, API and contract testing, load tests with k6, mutation and property-based testing, flaky test triage and CI test selection.
curl -fsSL codexskills.dev/install.sh | sh -s -- --category testing Installs all 32 into ~/.agents/skills/. Or download the zip.
All 32 Testing & QA skills
Each opens the full SKILL.md, example prompts and every way to install it.
-
Accessibility Testing
axe in CI, humans for what axe cannot see -
API Mocking with MSW
Mock the network, not your fetch client -
API Testing
Every status a client must handle, checked over HTTP -
Benchmark Testing
Prove it is faster, with error bars -
Chaos Engineering
Break it on purpose, with a hypothesis -
Contract Testing
Catch cross-service breakage before either side deploys -
Coverage Analysis
Gate the diff, ratchet the total, read the gaps -
Cypress E2E
Aliased intercepts and cached sessions, no fixed waits -
Flaky Test Triage
Name the cause, prove the fix, retire the retry -
Fuzz Testing
Throw a million inputs at your parser first -
Go Testing
Table tests, race-clean, runnable one case at a time -
Integration Testing
Test the seams where production actually breaks -
Jest Testing
Mocks that reset, timers that advance, Jest that exits -
JUnit 5 with AssertJ and Mockito
Jupiter tests that are discovered, strict and fluent -
Load Testing with k6
Answer a capacity question, not just draw a chart -
Mobile E2E Testing
Few journeys, stable ids, green on every run -
Mutation Testing
Find the bugs your green test suite would ship -
Playwright E2E
Role locators, one login, a trace for every flake -
Property-Based Testing
State the rule, let the library hunt the counterexample -
pytest Testing
Fixtures scoped right, cases named, suites parallel -
React Testing Library
Find it by role, click it like a user -
RSpec Testing
Specs that read as sentences and skip needless rows -
Selenium WebDriver
Explicit waits, stable locators, a pinned Grid -
Snapshot Testing
Snapshots small enough to actually review -
Test Data Factories
Valid by default, special only where it matters -
Test Impact Analysis
Run the tests a change can break, nothing more -
Test Plan Writing
A QA plan ranked by risk, not by habit -
Test Strategy
Pick the test mix from risks, not diagrams -
Testcontainers
Test against real Postgres, not a lookalike -
Unit Testing Patterns
Tests that survive refactors and fail for one reason -
Visual Regression Testing
Every pixel diff is real, every baseline reviewed -
Vitest Testing
Hoisted mocks, named projects, real-browser tests
No Testing & QA skill matches that.
Where to start
Install the ones that match requests you make every week. Name one with $flaky-test-triage when you want it for sure; otherwise Codex picks by description.
Start with
- Flaky Test TriageName the cause, prove the fix, retire the retry
- Playwright E2ERole locators, one login, a trace for every flake
- Accessibility Testingaxe in CI, humans for what axe cannot see
Install a few by name
curl -fsSL codexskills.dev/install.sh | sh -s -- accessibility-testing api-mocking-msw 104-line POSIX script. No sudo, no telemetry. Read install.sh
Testing & QA FAQ
How do I install every Testing & QA skill at once?
Run curl -fsSL https://codexskills.dev/install.sh | sh -s -- --category testing to put all 32 in ~/.agents/skills/, or add --project to install them into the current repository's .agents/skills/. You can also download the category zip and unpack it yourself.
Does installing 32 skills slow Codex down?
Hardly. At startup Codex sees only each skill's name and description, a few dozen words apiece, and reads a full SKILL.md only when a task needs it. Install the whole category if the work fits; unused skills cost almost nothing.
Which Testing & QA skill should I start with?
Start with Flaky Test Triage, Playwright E2E, Accessibility Testing. They cover the requests that come up most in this category. Mention one with $flaky-test-triage to try it.