tdd-workflow

Enforce Test-Driven Development with tests before implementation and 80% coverage.

17|1|Updated Apr 20, 2022
One-click install
npx skills add https://github.com/jvegaf/harmony --skill tdd-workflow-jvegaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/jvegaf/harmony/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/jvegaf/harmony --skill tdd-workflow-jvegaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Mandatory Tests First: Guides users to write tests before implementing code.
  • Comprehensive Coverage: Enforces minimum 80% coverage across unit, integration, and E2E tests.
  • Use Case: When starting a new feature, use this skill to first define user journeys, generate failing test cases, implement code to pass tests, and finally refactor and verify coverage.

Quick Start

Activate this skill when you begin writing new code to ensure tests are created first.

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 for new features and refactoring?

To enforce test-driven development, this workflow mandates writing tests before implementation and guides you through defining user journeys, generating failing tests, and verifying code to achieve over 80% coverage.

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

The minimum code coverage required is 80%, which must be achieved across your unit, integration, and e2e tests to ensure robust software quality before implementation is finalized.

How do I start writing tests first when developing new code?

To start writing tests first, activate this workflow to define user journeys, generate the initial failing test cases, implement the code to pass those tests, and finally refactor while verifying coverage.

Does this test-driven workflow support e2e tests with Playwright?

Yes, this workflow supports establishing testing patterns and utilizing tools like Playwright to define user journeys and generate end-to-end tests for verifying robust code quality.

Can I use this workflow for bug fixes and refactoring?

Yes, you can use this workflow for bug fixes and refactoring, as it enforces Test-Driven Development principles by mandating that tests are written before implementing the actual code changes.