skills.rest
thanhquan3010
thanhquan3010COMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce Test-Driven Development with 80% coverage across unit, integration, and E2E tests.

Updated Mar 7, 2026
Search Tags:#unit tests#testing#tdd#integration tests#code coverage#e2e tests#playwright
One-click install
npx skills add https://github.com/thanhquan3010/hospital-service-management-system --skill tdd-workflow-thanhquan3010
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/thanhquan3010/hospital-service-management-system/tree/main/.agent/skills/tdd-workflow
Command: npx skills add https://github.com/thanhquan3010/hospital-service-management-system --skill tdd-workflow-thanhquan3010

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures all code development adheres to Test-Driven Development (TDD) principles, guaranteeing high test coverage and robust software quality.

Core Features & Use Cases

  • Test-First Development: Guides users to write tests before writing implementation code.
  • Comprehensive Coverage: Mandates minimum 80% coverage across unit, integration, and E2E tests.
  • Use Case: When developing a new user authentication feature, use this skill to first define tests for registration, login, and logout, then write the code to satisfy those tests.

Quick Start

Use the tdd-workflow skill to write tests before implementing the new user profile API endpoint.

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 (TDD) when writing new software features?▼

Enforce Test-Driven Development (TDD) by guiding the process from user journey definition to test case generation before implementation. This workflow mandates writing tests first to guarantee robust software quality and high code coverage.

What is the minimum code coverage required for unit, integration, and e2e tests?▼

Minimum code coverage requires 80% across unit tests, integration tests, and e2e tests. This comprehensive coverage mandate ensures that all new features, bug fixes, and refactoring tasks maintain robust software quality.

How do I write tests before implementation for a new user profile API endpoint?▼

Write tests before implementation by first defining user journeys and generating test cases for the API endpoint. Once tests are established, write the implementation code to satisfy those tests and verify coverage.

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

Yes, this TDD workflow supports end-to-end testing with Playwright. It guides the creation of e2e tests alongside unit and integration tests to ensure comprehensive coverage and validate complete user journeys.

When should I use a test-first development workflow for bug fixes and refactoring?▼

Use test-first development for bug fixes and refactoring to prevent regressions and ensure robust code. The workflow mandates defining test cases before altering implementation code, guaranteeing minimum 80% coverage for all modifications.

Related Skills

Explore More Software Engineering Skills→
vlad-ryzhkovvlad-ryzhkov
25

repo-scout

Audit Go backend repositories for API endpoints, infrastructure, and test coverage.

Community
Intermediate
LuohaothuLuohaothu
24

test-coverage

Analyze coverage reports and flag files below the 80% threshold.

Community
Advanced
aayushsoamaayushsoam
1

tdd-workflow

Automate test-driven development workflows enforcing tests-before-code with 80% coverage.

Community
Advanced
fcnatrafcnatra

bdd-with-approvals

Create executable BDD specifications and scannable approval tests.

Community
Intermediate