|
|
Activity:
Question posted: 07 14 2008 05:49:59 +0000,
3 answers, 244 views, last activity
07 06 2010 20:18:08 +0000
|
|
|
|
That is an oft repeated question Rohini!
The testing team is expected to detect bugs before delivery, but, I have not seen a bug free software in my career.
It is exactly to deal with situations like these that the test plans and test cases need to be reviewed and approved by the Customer.
If the test cases have been reviewed and all test scenarios have been approved, the probability of having to take the entire blame is much lesser.
Moreover, if the review and approval has happened, it ensures that even if bugs are still found by customer, they are of lesser criticality.
At the end of the day, the test engineers ARE supposed to try and minimise this risk.
My advice is, Learn something from this. First of all accept the blame (atleast part of it :))
Log the issue, track it, ensure that you have test cases written for it. Secondly, try and analyse how the issue escaped detection in the first place and put in some preventive measures so that you or one of your team mates do not repeat the same mistake.
As a test engineer, you will definitely face more such issues in your career, do not get bogged down by it.
All the best.
Ravi

|
|
|
|
|
|
|
|
|
|
I agree.. thanks for the reply... I just wanted to know how to minimize the risk of getting the balme.. :) and you have showed me the right path for it.. Thanks!!! Rohini |
When customer reports an issue, then is it correct to put all the blame on testing team and held them responsible for the bug reported? |
I feel testing is very essential part of SDLC (software development life cycle) that helps you to come up with quality product, so it is no way a small fry's job.. It has to be very intense and should be done by professionals as development is done by... |