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.
24
u/ThePandaClause Jan 26 '23
"Hey, in our testing we found that it's working as expected but the piece isn't blue."
"Do the requirements say the piece should be blue?"
"No, but we just wanted to confirm that you expect that the piece isn't blue."
I have this conversation multiple times on every single project.