test-driven-development

To start Test-Driven Development with pytest, write a failing test first, execute it using specific pytest commands to verify the failure, then write minimal code to pass the test before refactoring.

The standard TDD cycle for software testing involves writing a failing test first, implementing minimal code to make the test pass, and finally refactoring the code without breaking the passing tests.

You should use TDD practices in your programming workflow when you need to enhance software quality and reliability by ensuring all code is developed with tests written before the implementation.

You run specific unit tests to verify TDD behavior in pytest by executing commands like `pytest tests/test_feature.py::test_specific_behavior -v` to check failures and passing states.

Common mistakes to avoid when implementing Test-Driven Development include skipping the initial failing test step or writing excessive code before verifying test passes, which TDD guidance helps troubleshoot and prevent.

TDD requires the pytest framework to enforce the testing workflow, but the Skill itself operates without external dependencies, utilizing internal scripts to guide the development process.