Testing is Rocket Science Not Brain Surgery

We’re here to benefit the testing community overall so it’s prudent to help out on a few of the real issues you’ll face on the job. The goal of this series is to help you settle the hard questions whose answers you may have taken for granted when you signed up for this mission. If you only take one thing away from this blog, let it be this, DO NOT TAKE ANYTHING FOR GRANTED!

There, you’ve been warned, with capital letters to boot. I could almost rest on that statement alone and end this series, but that would be a disservice to the enormity of the error in not addressing the specifics. So over the next few weeks we will explore the big ones, the issues that leave you thinking to yourself, “Why did they even post this requirement, now what do I do that I’m here on-site?”

Addendum:

Thanks to Ben Simo’s contributions at Quality Frog the idea of “Defensive Pessimism” was brought to my attention. This archetype is actually a good place to start for the performance tester, but as with all things it should be used in moderation.