> Teams can create whatever rules they want or name things whatever > way they wish to.
I'm not sure I agree with this. Communication across teams and the industry is important too. Why muddy the waters by everybody defining things as they like? The whole idea of design patterns is to apply a shared vocabulary to common patterns in code. Maybe unit tests are just a design pattern...
I think you should stick to your strict definition, but I think these other kinds of tests need a good name. What if you are developing an OS, a database, etc.? You need to have plenty of tests, whether you call them unit or something else. How would you do TTD development on these things if you were limited to unit tests? Or is TDD not limited to unit tests?
Flat View: This topic has 50 replies
on 51 pages
[
«
|
282930313233343536
|
»
]
Previous Topic
