As a QA learning to say No is very important skill while proving not being a blocker-try to be polite, confident enough to say why you are saying No with reasons and example no to last minute changes in sprint, Say no more when the QA time is used for development in previous sprints, when the sign off release, when goals are set too high to be achieved, when others start questioning your estimation, Saying No more to 100% automation when the product is in the early phase when requirement is not clear and stable

As a tester, I’ve heard it all — but the classic “just 20 more minutes” from devs hits different.

Fast forward 8 hours later:
I’m still refreshing the page,
Staring at the same 503 error like it’s part of my test data set,
Hoping something… anything… will load.

Deployments? Broken.
Sanity? Questionable.
Hope? Rapidly declining.

But hey — at least the error page loads faster than the app! 🤣

Classic words from Ben Dowen during an episode of This Week in Testing.

What I saw last night will haunt your Jenkins logs forever. May your coffee be strong and your endpoints be stable.