I_suck_and_my_tests_are_order_dependent
I've noticed a lot of developers that have this kind of code purity complex where their way of doing things is superior even if the actual code Works - which I think is the number one most important thing about code.  The code purity complex is a self-limiting decision.Those developers will be sitting at home fuming, I guess, as I cheerfully build a new feature on VB6 code last changed in 1999 that relies on using "On Error resume next", on an obscene contract rate.Working only with Good code is a luxury decision, and writing Code That Sucks isn't necessarily bad, if thats the fastest/cheapest way to write code that works.  The end user almost as a rule, doesn't care about your code purity.  A developer probably couldn't even explain that purity in a way that would make the end user understand its value.  This method name indicates a lack of understanding that finding the right balance of speed, cost and quality is a compromise.Yes, tests that can run in isolation are "better".