I am working on a project, on that project developers are doing a very good job that we hardly find the bugs on that application. Everything is running very smoothly client is very happy with the developers. but now client think that we are not reporting bugs & we are not doing anything which is not true Now how to handle this situation. How to explain this thing to the client.
asked Jul 10, 2017 at 5:43
-
3Possible duplicate of What should Testers do if they are not able to find good defects in the product?– beatngu13Jul 10, 2017 at 5:45
-
I went through that Question but I couldn't find how to deal with the client in this situation.– Nitin RastogiJul 10, 2017 at 5:48
-
@BharatMane this is completely different from your refer Question.– Nitin RastogiJul 10, 2017 at 6:59
-
Possible duplicate of How can I switch from manual testing to writing automation?– Narendra ChandratreJul 10, 2017 at 8:38
-
@NarendraC It's different from your refer one– Nitin RastogiJul 10, 2017 at 8:45
Add a comment
|
2 Answers
While testing this application I'm sure you might have documented your test plan and also the cases you executed for testing.
If so, you can share those documents with the client saying these are the cases we have executed and also share with the client your test coverage data to show which areas and scenarios you have covered. From that the client will get an idea what testing was done for the application.
You can also go through the test cases yourself to see if you have missed anything or see if you can come up with more cases to test the application with. Also share this report once you're done testing.
That way client will know that the application was tested properly and not many issues were found during testing. So they won't complain why a huge list of bugs has not been reported to them.
answered Jul 10, 2017 at 5:49
-
I agree with you, we did all the thing you mention but client believe that they are not getting ROI from Test Dept as everything is going very smooth. At the end client saying that he is getting a very good product without testing dept then why he spends money on testing. Jul 10, 2017 at 5:58
-
So, in your team testers aren't involved in requirement analysis and business scenario testing? Plus, if the product isn't tested at all and there is a bug to occur, will the client then come yelling at your dev team for not doing good work? Or will he accept the fact that he didn't invest in testing and hence this occurred (PS - testing also doesn't guarantee 100% bug free product)? Jul 10, 2017 at 6:02
-
Now he strongly believes that without testing he can have a very good product and I don't know how to break his belief. Jul 10, 2017 at 6:12
-
@nitinr, it may come down to use evidence; learn a lesson the hard way. Once he witnesses you can not alway have a good product without testing, then he will believe you.– Yu ZhangJul 10, 2017 at 6:17
-
@ Yu Zhang You are right brother, I know that at the end he will come to us when a product becomes more complex and required regression, But want to give one more try to explain him the importance of testing so that I don't lose the business. Jul 10, 2017 at 6:34
I'd like to add another view of QA engineer.
Do you have story during development phase to tell your client? Do you add value to the product? I bet you do as Quality Assurance. Go tell them.
Since we should be a QA rather than a tester. We do assurance the quality of software and quality is not a thing that only measure after developer finish the last line of code. Actually, Quality need to be addressed before developer start the first line of code.
With team, QA grooms the client's requirements with a view of system impact, usability, UX, and etc. QA produces test approach for positive and negative scenario. We plan for performance and failure test. ... blah blah blah it's a lot of thing QA do to assurance the quality.
Even if none of a single test is fail when we did a test. But I think the things, QA did affect developer and the software somehow. Maybe developer had go over our test cases and realized he missed a detail. Then the discuss was arranged and developer did a fix before he shipped the software to test.
This is just an example. I believe you did and you do these things already. If this kind of client issue happen again. Go tell them, what is the value that you add to software, not only the test cases that you test against it.
Good luck.
