skills.rest
arusinova
arusinovaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-workflow

Enforce test-driven development workflows with unit, integration, and E2E tests.

Updated Aug 23, 2026
Search Tags:#testing#tdd#development#e2e#unit-tests#integration-tests#test-coverage
One-click install
npx skills add https://github.com/arusinova/annarusinova-platform --skill tdd-workflow-arusinova
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/arusinova/annarusinova-platform/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/arusinova/annarusinova-platform --skill tdd-workflow-arusinova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies a disciplined TDD workflow to ensure code is written against tests, reducing defects and rework across feature development.

Core Features & Use Cases

  • Tests BEFORE Code: Always write tests before implementing functionality to guide design.
  • Coverage Target: Aim for 80%+ test coverage across unit, integration, and E2E tests.
  • Structured Workflow: From drafting user journeys to generating tests, implementing code, running tests, and refactoring.

Quick Start

Start by writing a minimal unit test for a new feature, then implement the simplest code to pass it.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce TDD practices across feature development to achieve 80%+ test coverage?▼

To enforce TDD and achieve 80%+ test coverage, you must write unit, integration, and E2E tests before implementing code for new features, bug fixes, and refactoring. This structured workflow ensures tests guide design and validate changes.

What is the proper workflow for writing tests before code during feature development?▼

The proper TDD workflow starts by drafting user journeys and writing minimal unit tests, then implementing the simplest code to pass them, running the tests, and finally refactoring while maintaining 80%+ overall coverage.

Does TDD require unit, integration, and E2E tests for every code change?▼

Yes, disciplined TDD requires unit, integration, and E2E tests to accompany every change, including new features, bug fixes, and refactoring, ensuring comprehensive validation and reducing defects across the codebase.

What's the best way to maintain 80%+ test coverage when refactoring existing code?▼

The best way to maintain 80%+ test coverage during refactoring is to ensure existing unit, integration, and E2E tests accompany the changes, running them continuously to validate that the structured workflow preserves functionality.

Can I use test-driven development for fixing bugs without breaking existing features?▼

Yes, you can use test-driven development for fixing bugs by writing tests that reproduce the bug before implementation. This ensures the fix accompanies the change and validates against regressions within the structured workflow.

Related Skills

Explore More Software Engineering Skills→
Ying-Kai-LiaoYing-Kai-Liao
1

tdd-workflow

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

Community
Advanced
koumatsumotokoumatsumoto

tdd-workflow

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

Community
Advanced
beratcelik1beratcelik1
1

python-testing

Apply pytest strategies for unit, integration, async, and database tests.

Community
Intermediate
mscipiomscipio

atdd

Generates executable test specifications for workflows using GanttProject's Umlet integration.

Community
Intermediate