TDD teaches people who aren't good at writing tests about the need for falsiability: that the test doesn't pass anyway without the code change. That goes out t

TDD teaches people who aren't good at writing tests about the need for falsiability: that the test doesn't pass anyway without the code change. That goes out the window after refactoring though. Tests created before refactoring continue to pass, but they are connected to changes that no longer exist and therefore could not be backed out to show that the tests fail. (Not without rolling back the refactoring). Or, tests that were connected to independent changes now cannot be easily made to fail independently. Refactoring tied them together. Thus they are redundant.