If you’re like me, one of the first things you do in the morning is check the results of the previous nights automated test runs. You site at your desk, cross your fingers, open up Jenkins, and hope to see a bunch of blue dots (PASS).
When a build fails it’s time to go into debugging mode. Automated test can fail for a lot of reasons. Sometimes just knowing what to look for can help you avoid the problem in the first place.
Let me tell you a quick story about a common situation.
A Developer walks into the office and instantly notices that something isn’t right. His spider senses are going off. The room is electric, there’s a panicked look on a co-works’ face, as they types furiously. The two people in Customer Support look like they’ve been hit by a bus. He pulls out his phone, checking his email expecting the worse. It’s flooded with email. There was a software patch last night but the manual test team didn’t find any critical issues. “What is going on?”, they think.