Skip to content

lidge-jun/codexclaw / plugins/codexclaw/skills/dev-testing

cxc-dev-testing

Unverified

Use for tests and release verification. Triggers: regression test, Playwright, E2E, contract test, coverage, CI flake, TDD, 테스트, 회귀 테스트, 품질 게이트.

Testing & QA

Balance: ~40% Backend/API, ~40% Frontend/E2E (Playwright), ~20% Cross-cutting (CI, Security, TDD, Coverage) -- directional guidance, not a hard ratio. Scope: test harnesses, fixtures, mock policy, runners, Playwright, CI gates, coverage. Root-cause analysis and debugging playbooks → dev-debugging.

  • This skill owns test adequacy; dev-code-reviewer owns finding severity and review process.
  • CI pipeline ownership and deployment verification: see dev-devops.
  • Data pipeline testing and ETL validation: see dev-data.
  • Design direction context for rendered verification: see dev-uiux-design. This skill activates by change-surface when work needs verification depth, regression coverage, or a reproducible test harness.

Class, fast path, rule authority, proof, and safety: dev. Current/public evidence: dev routing.

1.3 Risk-First Priorities

  1. auth / session / permission boundaries
  2. money movement, quota, credits
  3. data mutation and irreversible actions
  4. file upload / parsing / external webhooks
  5. shared API contracts used by frontend clients
  6. error paths, retries, rollback behavior

1.4 Harness Selector

ProblemPrimary HarnessAvoid
pure business ruleunit / service testbrowser test
route + middleware + serializationAPI integration testmocking the route itself
DB query / migration / transactionreal DB integration testfake repository for SQL correctness
frontend consuming backend JSONcontract testmanual-only verification
rendered critical flowPlaywright smokeasserting internal React state

Test-oracle rules apply before accepting green: oracle integrity.

Modular References

ConditionReference
Choose verification depth or test a CRUD slicecore/crud-test-matrix.md
Choose model, distribution, fixture policy, or general test rulestest-strategy.md
New feature unit/service/integration tests (not regression/contract)edge-first-testing.md
Property/invariant-heavy or mutation testingproperty-and-mutation-testing.md
Backend/API, database, or contract verificationapi-test-patterns.md; backend-testing.md
Rendered browser tests or exploratory browser QAbrowser-testing.md
CI test stages, failures, or flakesci-integration.md; ci-pipeline.md
ENFORCE_TDD, AI regressions, or test-induced production guardstdd-and-regressions.md
Accessibility, trace/log verification, security, coverage, or pre-flightacceptance-gates.md
Write acceptance criteriaacceptance-row-reachability.md
Test expectations, prose seams, override/default/fallback fixturestest-oracle-integrity.md
Implementation completion with test/config changespatch-integrity.md
Scarce, paid, rate-limited, or opaque evaluatorslimited-oracle-evaluation.md
Performance/load or C3+ production readinessload-testing.md
ML/LLM evaluation or quality gatesml-evaluation.md
Desktop suites and CI matrixNative desktop acceptance
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 318kUpdated Claude CodeCodexUnverifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 318kUpdated Claude CodeCodexUnverifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 318kUpdated Claude CodeCodexUnverifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 196kUpdated Claude CodeCodexVerifiedInstall