The tester’s version of “The Apprentice”
monica914 060000WAY8 Comments (2) Visits (1918)
A colleague shared this article with me and much of the thinking aligns with where I’ve been landing on the topic of continuous testing. Of course, when reading the article, one thing jumps right out …. When the author, Marnie Hutcheson, expressed concerns about being able to complete the testing in the time frame specified (30 hours of testing, twice, over a weekend), she was, um, fired.
Felt to me as abrupt as hearing “you’re fired” on a certain television show. And the most amazing part to me as a veteran tester for 20 years is the change in the role of the tester. There was a time where raising risk flags and voicing concerns about quality was what were *supposed* to do. So while we, in the test community, might not like it, the times they are a-changing. Whether we like it or not.
Which brings me back to Marnie’s other points about how to test (and survive) in the fast-paced world of continuous delivery and its cousin continuous testing. As I mentioned in an earlier blog, I think it really does mean testing less and focusing our automation efforts on deploying the test environment and test scripts for only those areas of critical or unrecoverable failure. I was really glad to see others thinking along the same lines. I have taken it a step further, to say if it can be fixed quickly, then don’t worry about it. Really, we only have to worry about the functional problems found in production. And yes, that does mean letting our end users do our testing. But the tolerance for that has gotten higher and higher thanks to Facebook and others. The key decision point is how fast to the fix? If it’s fast, then it’s fine. Time to start reducing our process, readjust our thinking and figure out how to deliver quality software by the new rules.