Applying TDD On Me
These books help me to applying Test-Driven Development on myself (not to drive company’s adoption). I’m interested in following answers from each book though they offer more:
Test-Driven Development: By Example
- What are encouraged habbitual practices in TDD? - Patterns for Test-Driven Development
Agile Testing: A Practical Guide for Testers and Agile Teams
- What is the purpose of testing? - Chapter 6
- As a developer, what exactly do I test and why? - Chapter 7 probably
- (Optional) How do other facets (or quadrant as coined by the book) affect developer? - Chapter 6 - 11 probably
xUnit Test Patterns: Refactoring Test Code
- What’s the Goal of Unit Testing? - Chapter 3, Chapter 6
- What is my phylosophy in unit test? For example should we test and code from outside-in or vice-versa? - Chapter 4
- What are principles of unit test? For example: should we prepare test data as a whole on the SUT or should we create them dynamically for each test? - Chapter 5
- What kinds of code are hard to test? - Chapter 15
- What are habbitual and technical patterns in unit test? - Part III
Test-Driven Development with Python: Obey the Testing Goat: Using Django, Selenium, and JavaScript
- What’s a concrete workflow to apply TDD with Python? - The whole book