data-driven-testing_skill

This skill helps you manage deprecated data-driven-testing guidance by guiding transition to testing-best-practices with strategy, matrix, and implementation

TypeScript

36

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill 0xbigboss/claude-code --skill data-driven-testing

SKILL.md829 B

Overview

This skill is deprecated and has been retired in favor of testing-best-practices. It previously provided a data-driven testing (DDT) configuration and generation approach focused on canonical JSON test-case schemas. For historical projects still using its outputs, it documents the migration path and key differences when moving to the replacement skill.

How this skill works

The skill examined test case definitions, fixture requirements, and a unit-focused DDT schema to produce structured test inputs and expected outputs. It validated that test data matched schema rules and flagged missing fixtures or inconsistent source locations. The replacement emphasizes broader test layering, markdown-based matrices, and strategy-driven output instead of rigid JSON blocks.

When to use it

You are maintaining legacy projects that still consume the DDT JSON schema and need guidance to migrate.
You need to understand why data-driven JSON test outputs were phased out and what to replace them with.
You want a checklist for converting existing DDT artifacts into layered test strategies and markdown matrices.
You require guidance on avoiding fabricated fixtures and invented source locations in test data.
You need to align old unit-only DDT outputs with modern CI lanes and e2e execution practices.

Best practices

Migrate from unit-only DDT to a layered test strategy: unit, integration, and e2e.
Replace rigid JSON test-case blocks with human-readable markdown matrices and strategy notes.
Avoid fabricating fixtures or inventing source locations — use real, auditable sources or recorded fixtures.
Design e2e tests to be idempotent and state-tolerant; plan for auth-state reuse where possible.
Separate CI lanes: fast PR smoke tests and full nightly suites with different coverage targets.

Example use cases

Converting a legacy JSON-based test suite into a strategy plus markdown-based test matrix.
Updating CI to run quick PR smoke tests while scheduling full DDT-to-strategy migration overnight.
Refactoring tests to remove fabricated fixtures and swap in recorded or mocked-but-realistic fixtures.
Designing e2e execution plans with preflight checks, async polling strategies, and flake handling.

FAQ

No. This skill is deprecated. Use testing-best-practices for all new test design, case generation, and strategy work.

What are the main differences compared to the new approach?

The new approach centers on test layering (unit/integration/e2e), markdown matrices instead of rigid JSON, strategy-driven outputs, and stricter rules against fabricated fixtures.