test-driven-development

Test-driven development enforces the RED-GREEN-REFACTOR cycle by requiring a failing test before writing production code, ensuring code is written with tests first. This methodology guarantees every feature or bug fix is accompanied by a failing test that validates behavior.

Yes, you can use real code instead of mocks during test-driven development. This approach ensures that tests truly reflect the actual behavior of the code, providing robust error handling and verifying that code changes do not break existing functionality.

You start test-driven development by installing the skill and running tests using the command `pytest tests/`. This initiates the automated TDD process, which enforces writing tests first to ensure code quality and maintainability across your software engineering projects.

Test-driven development requires testing frameworks like pytest to support writing test cases before production code. You need this dependency installed to execute the test suite and validate that your code changes adhere to strict TDD methodology practices.

The best way to ensure code changes do not break existing functionality is implementing test-driven development. By enforcing the RED-GREEN-REFACTOR cycle and using real code instead of mocks, you implement robust error handling and maintain safe code changes.

You should avoid using mocks in your test-driven development workflow when you need tests to truly reflect the behavior of the code. The methodology implements real code testing to ensure robust error handling and verify that code changes are safe and maintainable.