(these are taken from my real experiences over the past week or so)

You know you’re in trouble when…

  • Your dev says “I copied these statements from another developer. They’re too complex to explain.”
  • As you begin demoing strange AUT behavior to your dev, your dev drops a sharp F-bomb followed by a sigh.
  • You ask your dev what needs to be regression tested on account of their bug fix. They say “everything”.
  • After a migration you see an email from dev to DBA. The DBA responds “What are these delta scripts you speak of?”.
  • Your devs drop a prod patch at 5PM on a Friday as they all head home.
  • Dev says “Please try to repro the bug again, I didn’t do anything to fix it…I’m just hoping it got indirectly fixed”
  • Dev says “I marked the bug fixed but I have no way to test it.”
  • After a week of chasing and logging nasty intermittent bugs, you start seeing emails from your devs to your config managers saying stuff like “Why are these QA service endpoints still pointing to the old QA server?”
  • Your Config Manager says “Did you sanity test that patch I rolled out to prod when you were at lunch?”.
  • Your dev says “we don’t really care if the code we write is testable or not”.
  • Your bug gets rejected with the comment “It works on my box”.
What's on your list?


  1. Michael Kelly said...

    One from a couple weeks ago... You're pulling together a performance test plan and you ask what the upper limit is on size of file uploads and you just get a blank stare in return.

  2. Unknown said...

    when development rejects a defect with the comment "you shouldn't be doing that"

  3. anne-marie said...

    The software is fine...it's just the data and the sql server that are wrong !!?

  4. Alex said...

    Team City Build Summary:
    Build Succeeded!: 40 tests pass, 69 tests ignored.

  5. Anonymous said...

    Firefox?? Why would anyone use firefox? I haven't even got it installed. They should be using IE or Chrome.

    or when the programmer says
    "You can't do that...why would someone do that?"

    Or when you are spending more time updating bean count tallies and metrics than actually testing.


  6. Corissa said...

    Ironically, this was from the developer that forwarded me this post. While describing to me how to set up and use a feature: " (groan....) don't tell me you actually want to *test* this!"

  7. nulabs71 said...

    One from today...I told some of the dev's that some of the other dev's provide comments on QA defect tickets and that those where helpful to me. When I asked these other devs why they didn't do the same thing they said "nobody ever reads those" and "I don't have time for that"

    Uh, hello? Didn't I just say I read them?

    It's no coincidence that the devs who comment on their solutions have noticeably fewer defects in their code then the bunch that think there is no time for comments and no one reads them anyhow.

Copyright 2006| Blogger Templates by GeckoandFly modified and converted to Blogger Beta by Blogcrowds.
No part of the content or the blog may be reproduced without prior written permission.