lidge-jun/codexclaw / plugins/codexclaw/skills/dev-testing
cxc-dev-testing
VerifiedUse for tests and release verification. Triggers: regression test, Playwright, E2E, contract test, coverage, CI flake, TDD, 테스트, 회귀 테스트, 품질 게이트.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.2 KB |
| agents/openai.yaml | config | 164 B |
| examples/console_logging.py | script | 1.1 KB |
| examples/element_discovery.py | script | 1.5 KB |
| examples/static_html_automation.py | script | 1.1 KB |
| references/acceptance-gates.md | markdown | 3.4 KB |
| references/acceptance-row-reachability.md | markdown | 1.1 KB |
| references/api-test-patterns.md | markdown | 3.4 KB |
| references/backend-testing.md | markdown | 4.3 KB |
| references/browser-testing.md | markdown | 3.5 KB |
| references/ci-integration.md | markdown | 1.3 KB |
| references/ci-pipeline.md | markdown | 8.5 KB |
| references/core/crud-test-matrix.md | markdown | 2.2 KB |
| references/edge-first-testing.md | markdown | 2.5 KB |
| references/limited-oracle-evaluation.md | markdown | 2.7 KB |
| references/load-testing.md | markdown | 6.9 KB |
| references/ml-evaluation.md | markdown | 7.2 KB |
| references/patch-integrity.md | markdown | 1.4 KB |
| references/property-and-mutation-testing.md | markdown | 652 B |
| references/tdd-and-regressions.md | markdown | 5.4 KB |
| references/test-oracle-integrity.md | markdown | 2.0 KB |
| references/test-strategy.md | markdown | 1.5 KB |
| scripts/with_server.py | script | 3.6 KB |
references/edge-first-testing.md
View on GitHub# Edge-First Testing Workflow
## Principle
Write edge case tests BEFORE happy path tests. Most bugs hide at boundaries, not in the golden path. If you only have time for 5 tests, 4 should be edge cases.
## Test Order by Change Type
| Change Type | First Tests | Then |
|---|---|---|
| New API endpoint | Invalid input, auth failure, rate limit | Happy path |
| Data migration | Empty table, max-size row, concurrent write | Normal migration |
| UI component | Empty state, overflow text, disabled state | Normal render |
| Bug fix | Regression test for the bug | Related edges |
| Config change | Missing value, malformed value, env mismatch | Default behavior |
| Async workflow | Timeout, partial failure, retry exhaustion | Successful completion |
## Edge Case Matrix (11 Classes)
| Class | Examples |
|---|---|
| Boundary | 0, 1, MAX, MAX+1, negative |
| Empty | null, undefined, "", [], {} |
| Type coercion | "1" vs 1, true vs "true", NaN |
| Concurrency | Simultaneous writes, read-during-write, lock contention |
| Timeout | Network timeout, DB timeout, queue timeout, graceful vs hard |
| Permission | No auth, expired token, wrong role, revoked mid-session |
| Encoding | Unicode, emoji, RTL text, special chars (&, <, "), zero-width |
| Size | Extremely long strings, huge payloads, many items, 0 items |
| State | Uninitialized, mid-transition, corrupted, stale cache |
| Order | Out-of-order events, duplicate events, missing sequence |
| Environment | Missing env var, wrong timezone, disk full, DNS failure |
## Banned Patterns
| Pattern | Why | Fix |
|---|---|---|
| Testing only happy path first | Bugs cluster at boundaries; happy-path-only gives false confidence | Write edge tests first, happy path last |
| Mocking the thing you're testing | Proves nothing about real behavior | Mock dependencies, not the subject |
| Tests that pass with any implementation | Zero signal; test is decorative | Assert specific outputs for specific inputs |
| Copy-paste test with one value changed | Hides missing edge classes | Use the 11-class matrix above systematically |
| Asserting no error instead of correct result | Passes on silent wrong output | Assert the exact expected value |
## Definition of Done
- Edge coverage >= happy path coverage (measure by test count per class)
- Every class from the matrix above is represented OR explicitly marked N/A with reason
- Regression test exists for every bug fix before the fix is applied
- No test passes when the implementation is deleted or replaced with a stub
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| 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: 196k | Updated | Claude CodeCodex | Verified | Install |