Ayende @ Rahienhttp://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660Mickael Sauvee commented on Why you should test code too silly to breakThese lines of code are not siily as they implement some "behaviour" ... or desired features. I agree they have a very low risk to break... unless a full rewrite which has a higher risk to occur :-) http://ayende.com/3367/why-you-should-test-code-too-silly-to-break#comment3http://ayende.com/3367/why-you-should-test-code-too-silly-to-break#comment3Mon, 16 Jun 2008 07:08:13 GMTAlex Simkin commented on Why you should test code too silly to break@Ayende "I wrote a test for this piece [of] code:" If you wrote test first there would be no question. http://ayende.com/3367/why-you-should-test-code-too-silly-to-break#comment2http://ayende.com/3367/why-you-should-test-code-too-silly-to-break#comment2Sat, 14 Jun 2008 16:26:08 GMTShawn Neal commented on Why you should test code too silly to breakIf that's silly, then I guess I do silly things too. Confirming items get populated in the property bag or the correct view gets selected is actually relevant IMO, especially when it comes time to refactor/change the controller. My tests like that have saved me before, especially when you consider the cost of writing the tests is really low. http://ayende.com/3367/why-you-should-test-code-too-silly-to-break#comment1http://ayende.com/3367/why-you-should-test-code-too-silly-to-break#comment1Sat, 14 Jun 2008 04:34:19 GMT