tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: lzx0122

Enforce test-driven development with 80%+ coverage across unit, integration, and E2E tests.

Updated Jan 18, 2026

Search Tags:#testing #tdd #e2e #code-quality #playwright #unit-testing #integration-testing

Ready to run

npx skills add https://github.com/lzx0122/NigPing --skill tdd-workflow-lzx0122

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/lzx0122/NigPing/tree/main/.agent/skills/tdd-workflow
Command: npx skills add https://github.com/lzx0122/NigPing --skill tdd-workflow-lzx0122

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes disciplined software development by ensuring tests accompany new features, bugs are fixed, and refactors are validated with 80%+ coverage across unit, integration, and E2E tests.

Core Features & Use Cases

Enforce Tests-First: ALWAYS write tests before code to guide implementation and reduce regressions.
Coverage and Quality: Achieve a minimum 80% overall test coverage with comprehensive edge-case and error-path testing.
Test Types Supported: Unit, Integration, and E2E tests (Playwright) with clear run and verification steps.

Quick Start

Write a failing unit test for a new feature, then implement the minimal code to make the test pass.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce test-driven development before writing feature code?▼

To enforce test-driven development, always write a failing test before implementing the minimal code required to pass it. This tests-first approach guides implementation and reduces regressions across new features, bug fixes, and refactoring tasks.

What is the minimum test coverage required for unit and integration testing?▼

The minimum test coverage required for unit, integration, and E2E testing is 80% overall. Achieving this 80% coverage target demands comprehensive validation of both edge cases and error paths to ensure high code quality.

Does this TDD workflow support end-to-end testing with Playwright?▼

Yes, this TDD workflow supports end-to-end testing with Playwright. It explicitly covers unit, integration, and E2E test types, providing clear run and verification steps for validating features in your software projects.

How do I start TDD for a new feature?▼

To start TDD for a new feature, write a failing unit test that defines the expected behavior, then implement the minimal code to make the test pass. This ensures tests precede code implementation and guides your development process.

What testing types are supported when refactoring existing code?▼

When refactoring existing code, unit, integration, and end-to-end tests are supported. Validating refactors with these test types ensures disciplined software development and prevents regressions across your software project.