data-driven-testing
Deprecated
This skill has been replaced by testing-best-practices.
Use testing-best-practices for all test design, test case generation, and test strategy work.
What changed
- Test layering policy (unit / integration / e2e) replaces the unit-only DDT focus.
- Markdown tables replace the rigid canonical JSON test-case schema.
- Output is strategy + matrix + implementation plan, not JSON blocks.
- Added: hard rules against fabricated fixtures and invented source locations.
- Added: e2e execution guidance (preflight, async polling, flake handling).
- Added: CI lane guidance (PR smoke vs nightly full).
- Auth-state reuse and idempotent/state-tolerant e2e are first-class concerns.
More from 0xbigboss/claude-code
react-best-practices
Use when reading or writing React components (.tsx, .jsx files with React imports).
2.6Ktypescript-best-practices
Use when reading or writing TypeScript or JavaScript files (.ts, .tsx, .js, tsconfig.json).
2.1Kpython-best-practices
Use when reading or writing Python files (.py, pyproject.toml, requirements.txt).
1.3Kweb-fetch
Fetches web content as clean markdown by preferring markdown-native responses and falling back to selector-based HTML extraction. Use for documentation, articles, and reference pages at http/https URLs.
780zig-best-practices
Use when reading or writing Zig files (.zig, build.zig, build.zig.zon).
349nix-best-practices
Use when working with Nix flakes, overlays, shell.nix, or flake.nix files.
318