skills.rest
llmh333
llmh333COMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce a test-first workflow with unit, integration, and Playwright E2E tests.

Updated Sep 13, 2025
Search Tags:#tdd#integration testing#unit testing#code coverage#test strategy#playwright#e2e testing
One-click install
npx skills add https://github.com/llmh333/employee_management_spring --skill tdd-workflow-llmh333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/llmh333/employee_management_spring/tree/main/.gemini/skills/tdd-workflow
Command: npx skills add https://github.com/llmh333/employee_management_spring --skill tdd-workflow-llmh333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents regressions and quality drift by enforcing a test-driven development workflow where automated tests are written before production code.

Core Features & Use Cases

  • Test-first implementation: Write tests first, then implement the minimum code needed to make them pass.
  • Coverage enforcement (80%+): Combine unit, integration, and E2E coverage targets to ensure edge cases, error paths, and boundary conditions are validated.
  • End-to-end confidence (Playwright): Verify critical user journeys through browser automation and resilient, user-facing assertions.
  • Use Case: When adding a new API endpoint or refactoring existing logic, define the expected behavior via unit/integration tests first, then validate the full workflow with E2E tests.

Quick Start

Use the tdd-workflow skill by asking it to generate a unit, integration, and Playwright E2E test plan for your new feature, then guide you to implement code until all tests pass with 80%+ coverage.

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 backend features and API endpoints?▼

To enforce test-driven development for new backend features, write automated unit and integration tests defining behavior before implementation, then run a fix loop until all tests pass with 80%+ coverage.

What's the best way to validate critical user journeys with Playwright E2E tests?▼

Validating critical user journeys with Playwright E2E tests involves verifying complete user workflows through browser automation and applying resilient assertions to confirm full end-to-end behavior.

How does a test-first workflow prevent regressions when refactoring services?▼

A test-first workflow prevents regressions when refactoring services by defining expected behavior through automated tests before changing code, ensuring edge cases and error paths are validated against the new logic.

Can I use this TDD workflow to cover edge cases and boundary conditions in my code?▼

You can use a TDD workflow to cover edge cases, error scenarios, and boundary conditions by enforcing a minimum 80%+ coverage threshold across combined unit, integration, and E2E validation tests.

How do I implement code after generating a test plan for a new feature?▼

To implement code after generating a test plan, write the minimum production code needed to make the failing tests pass, iterating through a run-then-fix loop until all tests are green and coverage targets are met.

Related Skills

Explore More Software Engineering Skills→
Ard2pArd2p

aif

Analyze a project tech stack, install skills from skills.sh, and configure MCP servers.

Community
Advanced
run6270run6270
1

tdd-workflow

Enforce test-first development with 80% coverage using Jest and Playwright.

Community
Advanced
nahisahonahisaho
12

test-engineer

Design and implement unit, integration, and E2E tests for frontend and backend codebases.

Community
Advanced
Chachamaru127Chachamaru127
3.0k

impl

Implement features from Plans.md with tests in a Next.js/TypeScript stack.

Community
Intermediate