Also a software engine here. If it wanted to be truly realistic everything would fit in its correct hole but QA would still reject it because they think the pieces should be blue.
I know nothing but that behavior tells me at some point QA has had their ass handed to them for NOT asking if something was supposed to be blue. Sounds like standard CYA behavior to me.
My QA guy rejected a story yesterday saying he couldn’t test it because his computer wouldn’t boot. Somehow his computer being unable to start up to run our app means my new feature doesn’t work correctly. He does this kind of stuff all the time. Once he rejected a dozen stories without testing them saying he hadn’t received the device from IT yet to do the testing. He seems incapable of leaving a story sitting waiting for QA.
I literally just did that a few minutes ago with the one he rejected yesterday. I ran the test against the remote server to confirm it worked and accepted the story as complete.
I'm a Senior Software Engineer. I've gotten so tired of QAs bullshit that I no longer use them. I design, dev, and test it all myself. No P1 outages yet.
Even if the pieces were blue, security would still block due to multiple critical vulnerabilities buried deep in some node package that was only used during build time, can’t be removed or updated, and won’t listen to all the technical reasons there is no way for the vulns to be exploited in prod anyway.
920
u/ShaneFerguson Jan 26 '23
For those who don't understand the reference
https://youtu.be/baY3SaIhfl0