10 ways to annoy a Tester

Hadn’t posted anything for awhile, so thought this might be funny.  I’m sure i’m missing some really good ones though.
  1. “It works on my machine”
  2. If the Developers help test the Software, then what are the Testers going to do?
  3. “It’ll only take me a few minutes to write the code”
  4. “It’s a 1 line code change”
  5. “Don’t worry, i’ll explain how it works later, it’s pretty straight forward”
  6. During the last day of the Sprint  — “I have time to bring more work into the Sprint, but i’m not sure if there is enough time to test it”
  7. Add functionality that was not requested
  8. Make a change to a part of the system that was not planned, and then don’t communicate it to the Tester
  9. Talk to the Product Owner without a Tester present, and then misrepresent the business requirements
  10. “That’s an implementation detail”
Advertisements
  1. #1 by randymelder on June 18, 2012 - 5:08 am

    If there’s a problem with my code, QA will find it.

  2. #2 by Rani on September 17, 2014 - 11:19 am

    “It’s by design”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: