tdd-workflow

Enforce Test-Driven Development with 80% code coverage using Jest and Playwright.

4|1|Updated Mar 14, 2026

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

Ready to run

npx skills add https://github.com/GPTtang/skill-atlas --skill tdd-workflow-gpttang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/GPTtang/skill-atlas/tree/main/skills/devops/tdd-workflow
Command: npx skills add https://github.com/GPTtang/skill-atlas --skill tdd-workflow-gpttang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enforces Test-Driven Development (TDD) to ensure high-quality, robust, and maintainable code by requiring comprehensive test coverage before and during development.

Core Features & Use Cases

Mandatory Test-Driven Development: Guarantees tests are written before implementation.
80%+ Test Coverage: Enforces minimum coverage across unit, integration, and E2E tests.
Comprehensive Testing: Covers edge cases, error scenarios, and boundary conditions.
Use Case: When developing a new API endpoint, this Skill will guide you to write tests for its functionality, error handling, and integration with the database before writing the actual API code.

Quick Start

Use the tdd-workflow skill to develop new features by writing tests first, then implementing the code to pass those tests.

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 when writing new API endpoints?▼

Test-driven development is enforced by guiding you to write unit, integration, and E2E tests for functionality and error handling before implementing the actual API code to ensure robust coverage.

How do I maintain 80% code coverage across unit, integration, and E2E tests?▼

You maintain 80% code coverage by using Jest and Playwright to write tests first, implement code to pass them, refactor, and then verify coverage using dedicated reporting tools.

What is the best way to start writing tests before code for new features and bug fixes?▼

The best way to start writing tests before code is to follow the TDD workflow: write tests for edge cases and boundary conditions first, then implement the minimum code required to pass those tests.

Can I use Playwright and Jest to enforce TDD for refactoring existing code?▼

Yes, you can use Playwright and Jest to enforce TDD for refactoring by requiring comprehensive test coverage and verifying existing behavior through end-to-end and unit tests before making code changes.

How do I cover edge cases and error scenarios when following a TDD workflow?▼

You cover edge cases and error scenarios by writing tests that explicitly target boundary conditions and error handling requirements before developing the core feature logic during the TDD workflow.

Why does writing tests first improve code quality during bug fixes?▼

Writing tests first improves code quality by ensuring bug fixes and new features are validated against comprehensive test coverage, preventing regressions and enforcing robust, maintainable code.