Results for “test-driven-development”

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Writes a single failing test that reproduces a bug after its root-cause analysis is complete, before any fix is written. TRIGGER when: a bug has a completed root-cause analysis and you need the failing reproduction test, writing a test that proves a bug exists, the second step of the bug-fixing pipeline. DO NOT TRIGGER when: still triaging or diagnosing the bug → opsmill-dev-analyzing-bugs; implementing the fix once the test exists → opsmill-dev-fixing-bugs; general feature test-first work → superpowers test-driven-development.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

TDD: enforce RED-GREEN-REFACTOR, tests before code.

The English summary is being prepared. Showing the original description.

Plan, implement, or review test driven development work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests test driven development work.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Implements behavior changes with a test-first red-green-refactor loop: write one meaningful failing test, watch it fail for the intended reason, make the smallest change, then refactor while green. Use for new behavior, bug fixes, refactors with preserved contracts, and regression tests. Not required for disposable prototypes, generated files, or documentation-only edits.

The English summary is being prepared. Showing the original description.

Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

The English summary is being prepared. Showing the original description.

Write the failing test first, then the code that makes it pass.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.

The English summary is being prepared. Showing the original description.

Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.

The English summary is being prepared. Showing the original description.

在实现任何功能或修复 bug 时使用，在编写实现代码之前

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Implementing a feature, fixing a bug, refactoring — failing test first, then the code. For a WRONG test, `testing-anti-patterns` wins.

The English summary is being prepared. Showing the original description.

BEFORE writing/changing tests, mocks, or test-only methods on production classes — mocking-the-mock, production pollution, overfit assertions; for order, `test-driven-development` wins.

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Use when implementing any feature or bugfix, before writing implementation code

The English summary is being prepared. Showing the original description.

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

The English summary is being prepared. Showing the original description.