Can anyone tell me some good methologies of practising defect prevention in Testing Projects. What kind of defect prevention goals can be set for testing activities. What will be the kind of metrics i can monitor to make my testing project a success
Root Cause analysis will gives you to prevent the bugs in the next phase/project. there are somany methods like Ishikawa analysis, Fault tree analysis, cause & effect Analysis, pareto analysis etc.
you can try any of these methods for finding the root cause for some critical isseus and prevent them in the base level.
Do you really mean defects in testing project (wrong test cases, wrong defects submitted, defects not found, etc) - instead of a software defects? Testing can only find not prevent defects in software.
You could (for example) aim to reduce number of deferred defects (duplicated, wrongly reported, etc.) as well as ratio of defects fixed to defects detected after testing (in production).
Do you really understand your last statement? Do you really expect that simply monitoring something could guarantee success? In best case you will foresee the failure [img]/images/graemlins/smile.gif[/img]
Suggested reading: http://www.testingreflections.com/node/view/3055
[ QUOTE ]
Can anyone tell me some good methologies of practising defect prevention in Testing Projects.
[/ QUOTE ]
The only way to prevent software defects is to catch unclear, untestable, or contradictory requirements before they get to the design and code phase. Then if you have the technical knowledge, you can also sit in on code reviews to add your eyes to the process. There've been many instances where the test manager (me) has caught logic or process errors at that stage.
If you want to prevent defects from getting to the testers, a good method most developers detest is to automate their unit testing and incorporate those tests into your sandbox/dogfood/daily build process. That way defects introduced as the result of incompatible or poor coding will be caught prior to being introduced into your test environment.
If you want to prevent defects from getting into production, go into another industry. There is no such thing as 100% bug free code. All you can do is practice good testing methods, conduct test reviews, and get a lot of input from people outside the development bubble.
[ QUOTE ]
What will be the kind of metrics i can monitor to make my testing project a success
[/ QUOTE ]
Trust me, no matter what happens on a project you can always declare something a success. All it takes is creative rebranding of what it would have taken to succeed after the fact.