When you don't test EVERYTHING...

One component is used over 30,000 times. How many unit tests do you think we have for it? Zero. Fucking zero, Zip, Zilch, Nada, None.

WHAT THE QA FUCK!?

Any got fans here? Wise words from littlefinger.

Just... Fix them

The number of tabs open in Chrome is a direct correlation to the amount of coffee I need on any given day.

One day before beta is the wrong time to tell me you refactored the entire licensing module - and have zero test cases for it.

"Working as designed" : slang. The acceptance criteria were too hard, so we only completed half of them.

synonym: "not a bug"

If you're making code changes without a Story or Bug ID, you're doing something wrong. Take the 30 seconds and open a story to track your friggin work please.

The only thing worse than client QA is client vendor QA.

I do QA for a company that does custom implementations of a major e-commerce platform. On one of my current projects, the customer has elected to outsource their UAT, and isn't willing to wait for the site (or even individual features) to be complete before starting testing, so I've been triaging a lot of silly tickets. But today took the cake.

This system allows users to save their credit card info. The vendor QA guy filed a ticket "reporting" that if he saved a cc with a given number, then created a new cc record with the same number but a different expiration date, the original record was overwritten, rather than a new record being created.

I just stared at the thing for like five minutes, gathering the mental strength to reply with something other than "you're an idiot."

QA. Could you please help me solve this issue?
Dev. That's Server side, nothing to do with me! *proceeds to signal issue as 'solved'*

I’m a Frontend developer and my wife is Quality assurance Lead. We never tend to agree on things even personal. But with time I stepped up and developed negotiation skills. Now things are getting better 🙂

CoffeeReadyCallback() {
DrinkCoffee();
}

DrinkCoffee() {
QALife();
}

QALife() {
Throw TableFlip
//wait for more coffee to be ready
}

Should the QA team be allowed to make a judgement call?

I think it's more accurate when I (QA) show the developer the "fixed" bug ¯\_(ツ)_/¯