Talking testing, automation... and anything else.

Don’t Drive Angry…

My last couple of iterations have been challenging, to say the least. It’s early on in a new project with some big changes and we took on some stories that were, quite frankly, too large. And while they probably could/should have been broken down into smaller chunks, the team decided to take them on. Not surprisingly (in glorious hindsight), we all had a turn dealing with their frustrating vastness, and passed on the displeasure with each handoff. Luckily (sarcasm), with QA partaking in each facet of the process, and ultimately being the caboose, I got to enjoy the punishment of each facet–ba, dev and qa–end to end, as we each took a turn driving the angry train. Good times…

The last couple of retrospectives have been–shall we also say–less than enjoyable. There’s a reason finger pointing is NOT an olympic sport.

But the worst part was that I also got upset with myself. During said turmoil, and due to the number of changes (or so I thought), a number of my scripts started to fail… but because of the pressure to get these titanic stories done, I let them continue failing while I got caught up. Of course ONE of these scripts was failing because of a bug… but I wouldn’t find this out until an iteration later. Sadness…

The moral of the story isn’t really don’t drive angry, though this too isn’t bad advice… it’s to NOT let your automation fail… no matter what! We write automation to find bugs faster and to police change. Letting tests fail defeats both of these tasks and diminishes faith in the tests themselves. This is just foolishness… the sky may be falling but that’s not a reason to leave the skylight open! Bad QA; no biscuit.

Plusone Linkedin Facebook Twitter Digg Email

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.