test-driven-development

To enforce strict test-driven development, mandate the Red-Green-Refactor cycle by writing a failing test before any production code. This ensures tests are meaningful and prevents skipping tests entirely.

Common testing anti-patterns to avoid during refactoring include mocking behavior instead of testing real logic and polluting production code with test-only methods. Preventing these mistakes maintains code integrity.

Fix a bug using the Red-Green-Refactor cycle by first writing a failing test that reproduces the bug. Then, implement minimal production code to pass the test, ensuring the behavior is verified.

Yes, test-driven development prevents the accumulation of technical debt by eliminating the pitfall of writing tests after implementation. It ensures high code quality through strict cycle enforcement.

Yes, you can use this workflow for both feature implementation and bug fixes. It applies across software development lifecycles to ensure all production code is verified by a preceding failing test.

Writing a failing test before production code ensures the test is actually verifying the target behavior. This strict test-driven development enforcement guarantees minimal implementation and high quality assurance.