http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Jiggaboo, What is the association for that?http://ayende.com/160929/on-failing-tests#comment6http://ayende.com/160929/on-failing-tests#comment6Thu, 07 Feb 2013 19:26:45 GMTNow imagine you didn't have tests. I can't believe some people write software without tests.http://ayende.com/160929/on-failing-tests#comment5http://ayende.com/160929/on-failing-tests#comment5Thu, 07 Feb 2013 18:41:54 GMTFrank, But I am changing things all the time. As long as the behavior is functionally the same, I don't care.http://ayende.com/160929/on-failing-tests#comment4http://ayende.com/160929/on-failing-tests#comment4Thu, 07 Feb 2013 12:32:01 GMTBy break we both mean failing test, right? I was thinking more of making a logical blunder in e.g. a refactoring session. If your tests are meant to ensure that your system does what you expect it to do, then a failing test should say that after that change it does not behave in the same way. Hence, either your expectation shifted or you made a mistake.http://ayende.com/160929/on-failing-tests#comment3http://ayende.com/160929/on-failing-tests#comment3Thu, 07 Feb 2013 12:30:02 GMTFrank, That is pretty horrible from my point of view. If I make a change and something break, it means that it is very hard to make changes.http://ayende.com/160929/on-failing-tests#comment2http://ayende.com/160929/on-failing-tests#comment2Thu, 07 Feb 2013 12:00:03 GMTI don't know, when you do a change, and nothing breaks, there is some part of me that thinks that maybe the tests have an issue...http://ayende.com/160929/on-failing-tests#comment1http://ayende.com/160929/on-failing-tests#comment1Thu, 07 Feb 2013 10:42:39 GMT