data-driven-testing

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

Install with Tessl CLI

npx tessl i github:NeverSight/skills_feed --skill data-driven-testing

What are skills?

Review — 42%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

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
Commit: ff04dc7
Last updated: 9 days ago
Created: 9 days ago

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.