Comments by "" (@defeqel6537) on "Does TDD Rule Out Bad Ideas?" video.

@guttormvik6335 changing requirements should cause tests to change and then fail, which would give a good indication that the cause is in the implementation, unless there is a bug in the new test(s). Personally I prefer Beck's "developer tests" approach instead of unit/integration/etc. separation, usually this leads to testing rather large pieces of code, which makes refactoring rather easy, when the bigger test is too vague for me at a specific time, I might add an abstraction to the test, or make a smaller test to get the next step done. When I'm done, I often delete the smaller tests as the code is already covered by the bigger tests.
3
@amyIsFlexable requirements change -> create new test / delete old tests that are incompatible with new requirements, I'm not so sure what's difficult about that. The details of the tests depend on the project and libraries / frameworks used
3