skills.rest
J511Y
J511YCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Guides developers through strict TDD workflows with enforced 80% test coverage across unit, integration, and E2E tests using Jest, Vitest, Playwright, and mocking for APIs and external services.

Updated Jan 25, 2026
Search Tags:#testing#tdd#integration testing#unit testing#code coverage#playwright#e2e testing
One-click install
npx skills add https://github.com/J511Y/share-paint --skill tdd-workflow-j511y
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/J511Y/share-paint/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/J511Y/share-paint --skill tdd-workflow-j511y

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 comprehensive test coverage and robust, reliable software.

Core Features & Use Cases

  • Mandatory TDD: Enforces writing tests before implementation.
  • 80%+ Coverage: Requires a minimum of 80% coverage across unit, integration, and E2E tests.
  • Edge Case Handling: Ensures all edge cases, error scenarios, and boundary conditions are tested.
  • Use Case: When adding a new API endpoint, this Skill guides you through writing tests for success, failure, and edge cases before writing the actual API logic, ensuring the endpoint is reliable from the start.

Quick Start

Use the tdd-workflow skill to implement the 'user authentication' feature by first writing 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 adding a new API endpoint?▼

To enforce Test-Driven Development for a new API endpoint, you must write tests covering success, failure, and edge cases before implementing the actual API logic. This guarantees the endpoint is reliable from the start.

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

The minimum code coverage required for unit, integration, and E2E tests is 80%. This threshold ensures comprehensive handling of edge cases, error scenarios, and boundary conditions across all test suites.

How do I write E2E tests using Playwright within a TDD workflow?▼

To write E2E tests using Playwright within a TDD workflow, you follow a test-first approach for new features, bug fixes, and refactoring. This ensures robust software by validating end-to-end user flows before implementation.

Can I use Jest or Vitest for unit testing in a strict TDD workflow?▼

Yes, you can use Jest or Vitest for unit testing. The workflow mandates utilizing these frameworks to write unit tests before implementation, ensuring all boundary conditions and error scenarios are validated.

How do I handle API integration testing and external service mocking in TDD?▼

For API integration testing and external service mocking in TDD, you follow specific patterns to mock external services before writing the actual API logic. This ensures integration tests validate reliability without real external dependencies.

Related Skills

Explore More Software Engineering Skills→
yuhle-qugyuhle-qug

testing-expert

Provide Jest, Vitest Playwright and Testing Library guidance for JavaScript/TypeScript projects.

Community
Advanced
LuohaothuLuohaothu
24

test-coverage

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

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
gitkrakengitkraken
9.9k

add-test

Generate unit and end-to-end test files with templating for common frameworks.

Official
Intermediate