To measure how many bugs you found that were found by executing the Test Cases in your Software Design Document. When reporting a bug also include in this the Test Case identifier of the Test case that caused this bug to be found. Then run a query against you bug database to summarize the information you found.
The problem of identifying efficiency of your Test Cases is that you do not have all of the information you need; the missing information is “Total number of bugs present”. To identify efficiency a good calculation would be Total number of bugs found / Total number of bugs present .
A couple of scenarios for you:
Test Case 1 – using this tester finds 10 bugs – must be efficient, however if there were actually 50 bugs that could have been found this now becomes very inefficient. It may not be the Test Case that did not find these bugs it may be the skills of the Tester.
Test Case 2 – tester finds 0 bugs, must be inefficient or maybe it was that the code was developed correctly and there were no bugs to find – so maybe this Test Case is efficient.
You may have poor test cases but good testers in which case there is the probability that a lot of the defects will be found despite the poor test cases. Now you have inefficient test cases but the defect count will not necessarily show that.
You may have excellent test cases and less tat skilled testers and very few bugs are found. Now you have efficient Test Cases but the defect count will not necessarily show that.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison
[/ QUOTE ]If simple, why do you ask?? I am getting confused! [img]/images/graemlins/smile.gif[/img] Help!
[ QUOTE ]
how many bugs you found with your documents?
and how many bugs you found without them? (Tester experience). i need metric for this situation.
[/ QUOTE ]It appears that you just listed two "simple" metrics. It seems those would work if you want to measure something document-related. I am not certain that I would do that. Anyway, I am more confused than I was about 40 words ago??? Perhaps it is I who needs help???
If you are looking to characterize documentation defects, please consider reading some Michael Fagan or Tom Gilb works related to inspections and reviews.