<story><title>Testing is a separate skill and that’s why it can be frustrating</title><url>https://medium.com/planet-arkency/testing-is-a-separate-skill-and-thats-why-you-are-frustrated-7239b1500a6c#.s23ovtlo5</url></story><parent_chain></parent_chain><comment><author>koonsolo</author><text>The best testers that I know really enjoy breaking stuff. They have this special mission to break anything they get their hands on. They take great pride in finding the stuff that the developer probably didn&amp;#x27;t think of. They smile when it behaves weird, they laugh when it crashes. Their ego rises when they tell the developer that they were smarter.&lt;p&gt;And therefore, the one who built is, is not the person who makes it his lives mission to break it. Breaking it means more work, more searching for bugs, and then testing again. And nobody likes doing that. Except for awesome testers. They love looking at the face of a desperate developer getting frustrated by a nasty bug.</text></comment>
<story><title>Testing is a separate skill and that’s why it can be frustrating</title><url>https://medium.com/planet-arkency/testing-is-a-separate-skill-and-thats-why-you-are-frustrated-7239b1500a6c#.s23ovtlo5</url></story><parent_chain></parent_chain><comment><author>michaelfeathers</author><text>I don&amp;#x27;t think this is a good way of framing things. In fact int can be counter-productive.&lt;p&gt;Automated testing is the process of writing code to understand your code. We already have to understand our code. Testing is being deliberate about that understanding and writing it down. The same design&amp;#x2F;testing thoughts that lead us to edge cases can lead us their elimination without testing at all. It&amp;#x27;s an integrated process, not something separate.</text></comment>