Wait, I've never seen anyone recommend never changing the test - of course you may have to change it, if requirements change and it now tests the wrong thing, o

Wait, I've never seen anyone recommend never changing the test - of course you may have to change it, if requirements change and it now tests the wrong thing, or if you deleted the code it was testing, or if there's simply a bug in the test code. BDD encourages higher-level, whole-system tests alongside low-level unit tests, so the conditions for changing a behavioural spec should (hopefully!) happen less often, but I still don't see why you would avoid changing a test if it was wrong or no longer relevant.