Mar 31, 2016
My thoughts on coming in to work. This is going on day four of my test environment being broken in every possible way that I can’t (read: don’t have permission to) fix.
seen from United Kingdom
seen from China
seen from China
seen from Brazil
seen from Singapore
seen from Brazil
seen from Slovakia
seen from United States
seen from United Kingdom
seen from Brazil
seen from Brazil
seen from Philippines
seen from United States
seen from United States
seen from Malaysia
seen from Türkiye
seen from United Kingdom
seen from United States
seen from Slovakia
seen from United States
My thoughts on coming in to work. This is going on day four of my test environment being broken in every possible way that I can’t (read: don’t have permission to) fix.
My Reaction when, surprise surprise, all the things I identified as “I can’t test this so it’ll probably be broken when we release” are indeed broken.
My reaction when I let the team know that there are certain things I won’t be able to test until the code hits Production, and that they’ll all probably break.
"It magically goobity-goobities the thing!"
- my PM, earlier today
“I’m going to go in butt-first!”
- the other QA
Discrepancy
If you want your manual testers to spend more time finding bugs, then hire or train someone to automate the tedious things they do that hardly ever find bugs. Let your manual testers do what they do best, and don’t ask them to do something they specifically did not sign up for when they decided to be a manual tester. Really, this isn’t a huge leap of logic; telling manual testers that spending time on automation will free up their time is an insult, and creates a vast discrepancy between expectation and reality.
“Italian food is just like software!”
- the other QA
“I would put those wieners in and around the inside of my mouth!”
- the other QA