3 ms·
That's the right way to do TDD, see this talk: https://www.youtube.com/watch?v=EZ05e7EMOLM https://www.youtube.com/watch?v=EZ05e7EMOLM One of the above comment
by imran-iq 4y ago
That's the right way to do TDD, see this talk: https://www.youtube.com/watch?v=EZ05e7EMOLM https://www.youtube.com/watch?v=EZ05e7EMOLM
One of the above comments mentions BDD as a close cousin to TDD, but that is wrong as TDD is actually BDD as you should only be testing behaviours, which allow you to "fearlessly refactor"
- deleted 4y ago[deleted]
- bcrosby95 4y agoBehavior is an unfortunate term, because the "London Style" TDD sometimes is described as testing behaviors: https://softwareengineering.stackexchange.com/questions/123627/what-are-the-london-and-chicago-schools-of-tdd https://softwareengineering.stackexchange.com/questions/1236... Which seems like the exact opposite of what the talk is saying you should do.