|
You are here |
blog.8thlight.com | ||
| | | | |
blog.cleancoder.com
|
|
| | | | | [AI summary] Robert C. Martin discusses the pragmatic application of Test Driven Development (TDD), identifying specific scenarios where writing tests is too costly or unnecessary, such as for getters, setters, trivial functions, and GUIs, while reaffirming that significant production code should still adhere to TDD. | |
| | | | |
blog.cleancoder.com
|
|
| | | | | ||
| | | | |
blog.cleancoder.com
|
|
| | | | | [AI summary] Robert C. Martin discusses specific scenarios where Test Driven Development is impractical, such as when software controls physical devices or requires manual visual adjustment, arguing that applying the methodology to these layers constitutes a misuse of the practice. | |
| | | | |
www.tvagile.com
|
|
| | | [AI summary] The article advocates for programmers to step away from automated tests to focus on usability and the end-user experience during development. | ||