Enforce a TDD workflow with 80% code coverage across test types.
npx skills add https://github.com/ihj04982/my-cursor-settings --skill tdd-workflow-ihj04982
Please help me install this Agent Skill. Skill: tdd-workflow Source: https://github.com/ihj04982/my-cursor-settings/tree/main/skills/tdd-workflow Command: npx skills add https://github.com/ihj04982/my-cursor-settings --skill tdd-workflow-ihj04982
This Skill ensures all code development adheres to Test-Driven Development (TDD) principles, guaranteeing high test coverage and robust software quality.
Activate this skill to begin writing new code following the test-driven development process.
High-intent search queries and answers about installing and using this skill.
To enforce a test-driven development workflow, you mandate writing tests before implementation and follow the RED-GREEN-REFACTOR cycle. This process ensures features are well-tested from the start by guiding you to write tests first, implement code, and verify coverage.
The minimum code coverage required for unit, integration, and E2E tests is 80%. Enforcing this threshold across all test types guarantees high test coverage and robust software quality throughout the development process.
To apply the RED-GREEN-REFACTOR cycle, you first write a failing test (RED), implement the minimum code to pass it (GREEN), and then clean up the code without changing behavior (REFACTOR). This cycle guides structured test-driven development.
Strategies for mocking dependencies during integration testing include isolating the components under test by replacing external calls with controlled substitutes. This test-driven approach provides patterns for various test types to ensure accurate verification without side effects.
You need to write E2E tests versus unit tests in TDD when validating complete user workflows against isolated component logic. This test-driven approach requires comprehensive coverage across unit, integration, and end-to-end tests to ensure robust software quality.
Test-driven development works for refactoring existing code bases by using the REFACTOR stage to clean up code while ensuring existing tests remain green. This approach maintains high code coverage and robust software quality during structural improvements.
Dino-StarkAnalyze Python coverage.py results and propose tests for uncovered code paths.
sunholo-dataAnalyze test coverage to identify gaps, dead code, and brittleness.
ZESCODEValidate task completion via multi-agent tests, linting, and requirement checks.
haxlysConverts threat models and business context into actionable security requirements and test plans.
