slop-test-detector
Slop Test Detector
Agents generate tests that compile, pass, and increase coverage — but catch zero bugs. This skill detects those patterns programmatically.
When to use: Auditing existing test files for quality. Validating generated tests before writing them to disk. Enforcing the // Defect: comment convention.
When not to use: Evaluating test strategy (what to test). Measuring code coverage. Reviewing production code quality.
Rationalizations (Do Not Skip)
| Rationalization | Why It's Wrong | Required Action |
|---|---|---|
| "It compiles and passes" | Slop tests always pass — that's the problem | Run analyzeTestFile() and check must-fail findings |
| "It has a Defect comment" | Comment can be trivial or copied from the test name | Check trivial_defect_comment findings |
| "It has assert.ok(result)" | Truthiness checks pass for any non-null value | Verify assert.equal/deepEqual on specific values |
| "It increases coverage" | Coverage counts lines executed, not bugs caught | Check that assertions verify behavior, not just reachability |
More from apankov1/quality-engineering
pairwise-test-coverage
Combinatorial testing with a greedy pairwise matrix generator. Covers all factor pairs in near-minimal test cases.
18breaking-change-detector
Audit 6 categories of breaking changes with executable checks for contracts, API diffs, serialized state, and event types.
17websocket-client-resilience
Client-side WebSocket resilience patterns: backoff with jitter, circuit breakers, heartbeat hysteresis, command acknowledgment, sequence gap detection, and mobile-aware timeouts.
17barrier-concurrency-testing
Deterministic race condition testing using barriers and deferred promises. Replaces flaky setTimeout-based timing tests with reproducible interleaving control.
17fault-injection-testing
Use when testing what happens when things fail — storage errors, network timeouts, API 500s, service outages. Provides circuit breaker state machine, retry policies with exponential backoff, fault injection, and queue preservation assertions. Trigger on: 'circuit breaker test', 'retry logic', 'exponential backoff', 'what happens if the API fails', 'simulate network failure', 'fault injection', 'resilience test', 'queue preservation after crash', 'graceful degradation'. Skip for: happy-path unit tests, UI testing, or code review.
15zod-contract-testing
Validates Zod schema parsing at boundaries. Tests valid/invalid inputs, schema evolution, refinement coverage, and compound state matrices (2^N optional field combinations).
13