Feed from Testthisblog.com
(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?
Loading ...