If you are running short of time to perform exhaustive testing, you may follow the Risk Based approach. For that, pull out the all functionalities from SRS, list them down in a document so called RBT (Risk Based Testing) register. Each function is given a unique ID (like R001, R002 and so on). Now populate the two columns 'Probability' and 'Impact' for all functions. Trace out the Risk by formula 'Probability*Impact'. Higher the score, function will have more risk associated to it. Now, create test cases for 70% of high risk functions and execute them to ensure maximum coverage. You can leave the rest Low risk functions due to their less or almost no impact on system.
kawal
Apr 21st, 2006
Hi,
But my question is here that who will decide probability and imapct??
Regards
kawal
Guest
Jun 20th, 2006
With the help of business analyst (or similar kind of role, some projects will have Single Point Of Contact with the customer for requirements gathering ,updations) testing team will decide the impact and probability. Business analyst's inputs are important in the activit;y
Realizing you won't be able to test everything -how do you decide what to test?
Questions by satishss