Enforce a red-green-refactor workflow to reduce flaky tests across codebases.
npx skills add https://github.com/Ovid/smudge --skill writing-tests-ovid
Please help me install this Agent Skill. Skill: writing-tests Source: https://github.com/Ovid/smudge/tree/main/.claude/skills/writing-tests Command: npx skills add https://github.com/Ovid/smudge --skill writing-tests-ovid
This skill guides developers to write, modify, or review tests using a red-green-refactor workflow, reducing flaky tests and improving overall test quality.
Describe a failing test, implement the minimal code to pass, and refactor while keeping tests green.
High-intent search queries and answers about installing and using this skill.
You reduce flaky tests by enforcing a red-green-refactor workflow and applying deterministic mocking. This approach eliminates non-deterministic patterns, ensuring reliable early feedback across unit, integration, and e2e testing.
The red-green-refactor workflow is a test-driven cycle where you describe a failing test, implement minimal code to pass, and refactor while keeping tests green. It improves test structure and maintainability across the codebase.
Deterministic mocking improves test robustness by replacing volatile dependencies with predictable responses. This avoids flaky-test patterns and ensures tests pass consistently across unit and integration scenarios.
You need to review tests for flaky-test patterns when test reliability drops or early feedback becomes inconsistent. Applying red-green-refactor discipline during test modification or review identifies and removes non-deterministic behaviors.
Yes, you can apply red-green-refactor discipline to end-to-end testing scenarios. The workflow ensures test reliability and early feedback across unit, integration, and e2e environments by avoiding flaky patterns and applying deterministic mocks.
The best way to enforce test quality is following a red-green-refactor workflow with deterministic mocks and coverage practices. This reduces flaky tests and ensures reliable early feedback before shipping across the codebase.
xu-xiangEnforce test-driven development workflows with 80% coverage across unit, integration, and E2E tests.
ZaxbyHubIdentify technical debt and reliability issues in CI pipelines and test suites.
clostaunauCodify pytest conventions, AAA structure, fixtures, mocking, and coverage standards.
gztcodeEnforce a RED-GREEN-REFACTOR cycle by writing tests before implementation in Python.
