CtrlK
BlogDocsLog inGet started
Tessl Logo

data-driven-testing

DEPRECATED: Use testing-best-practices instead. This skill has been retired.

62

1.30x
Quality

41%

Does it follow best practices?

Impact

99%

1.30x

Average score across 3 eval scenarios

SecuritybySnyk

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xbigboss/claude-code/data-driven-testing/SKILL.md
SKILL.md
Quality
Evals
Security

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.
Repository
NeverSight/skills_feed
Path

data/skills-md/0xbigboss/claude-code/data-driven-testing/SKILL.md

Commit

e941209

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill