This question already has an answer here:
My question is similar to Leaving intentional bugs in code for testers to find:
We don't do this at our firm, but one of my friends says that his project manager asked every dev to add intentional bugs just before the product goes to QA...
...If you ignore the scenario were one of these intentional bugs gets shipped with the final product, what are the other drawbacks we should consider before even thinking of adopting this approach?
The difference is that I had different premises. I wanted to make a point without messing with anyone. Intended bugs not for motivation but for testing the testers, to point out that quality assurance process is dysfunctional.
I was working on a rather large and important feature. Critical part the of feature was that users could get a discount under certain circumstances. Problem that we had with that project was that QA was very sloppy and missed a lot of important bugs. On the other side project manager had a lot of faith in QA. In my opinion bad QA is worse than no QA, because it only adds illusions about quality. Couple of times I got into arguments with PM but I gave up and just decided that I should be my own tester and just assume that QA doesn't exist.
At some point a brilliant idea came to my mind - to test the QA. I found completely outrageous bug and decided that instead of fixing it I would leave it as is and see if the QA finds it. Bug was really bad. When user placed an order and got a discount, the browser redirects to payment provider and there user sees price without discount and is charged accordingly. This was a critical path bug.
Long story short, QA didn't find a bug, I fixed it before release of course and even created a ticket and politely announced it without blaming anyone to see the reaction. Both QA and PM didn't really cared, just said okay and that's it.
After that I finalized my conclusions about our QA but PM still had a lot of faith in him. I told some time after to assistant PM in private conversation, she told me to speak to his management, but I decided not to pursue and just carry on on my own because I really didn't know how to present the case.
So my questions are:
- Is it good idea to test testers by leaving bugs or even creating them?
- How to handle the situation where it happened, intentionally or not?
- How to otherwise point out low efficiency of QA?
- How to do it without forcing people losing face and creating tensions and conflicts?