4 ms·
> QA says: “it doesn’t work”. Dev says: “it must be working, all the tests pass”. I've never experienced this, and I'm kind of doubtful this is a true reaction
by gregmac 5y ago
> QA says: “it doesn’t work”. Dev says: “it must be working, all the tests pass”.
I've never experienced this, and I'm kind of doubtful this is a true reaction. I guess maybe it could happen in a team that is totally dysfunctional, where there's zero trust between QA and developers .. but in that case mocks are not the problem.
The realistic reaction is "huh, guess we are missing some test cases".
- fiddlerwoaroof 5y agoYeah, when I’ve run into this sort of bug, I always try to figure out how to make the unit tests reproduce the bug as a failing test case before attempting to fix the bug.
- emeraldd 5y ago> QA says: “it doesn’t work”. Dev says: “it must be working, all the tests pass”. Yup, the very next question here should be: Show me the failing/in correct behavior. This means: * There's a case the automated tests don't cover. * There's a misunderstood requirement on the QA or Dev side. * There's a broken machine or configuration in a deployment.