The project had a very high cost of testing. After going in detail, someone found out that the testers are spending their time on software that doesn’t have too many defects. How will you make sure that this is correct?
Total Answers and Comments: 4
Last Update: December 01, 2008 Asked by: sushkumar
RE: The project had a very high cost of testing. After...
May be we can have a look at the number of bugs logged for that against the numbers of scripts being executed. If the number of scripts being executed is relatively more then we can say that time is being wasted on a software that doesnt have too many defects
RE: The project had a very high cost of testing. After going in detail, someone found out that the testers are spending their time on software that doesn’t have too many defects. How will you make sure that this is correct?
If there is a bug fall rate and there has been no issues in the production....then one can stop testing
RE: The project had a very high cost of testing. After going in detail, someone found out that the testers are spending their time on software that doesn’t have too many defects. How will you make sure that this is correct?
First of all this would not have happened if the defect/functionality has been monitered. On the high costing test projects it is advisable to do Risk based testing than testing everything. Find out the high risk areas and test them first.
RE: The project had a very high cost of testing. After going in detail, someone found out that the testers are spending their time on software that doesn’t have too many defects. How will you make sure that this is correct?
First of all there is no guaranty that we must found the issues in all cases if there is no defects how can a tester can found? does he able to create the issues?? absolutey no.. So what i mean to say is if the application does or doesn't have the issues the entire testing has to be take place.
