Isn’t risk based testing just prioritisation?
Test managers routinely prioritise tests to fit in with the project’s schedule and the test resources available. Prioritisation is done based on the test manager’s, project manager’s opinions and the perceived needs of the business sponsoring the programme.
A risk based approach to testing takes a much deeper look at the real underlying needs of the project and what really matters to the end-customer.
By analysing the RISK of a failure occuring with a specific component or feature AND also the IMPACT of failure if that component or feature failed in a real-life situation, project resources can be more efficiently allocated to focus on testing what really matters in the limited time available.
A risk based testing (RBT) approach can help save time and reduce costs on your testing project.
August 10th, 2010 at 17:48
Hi,
Partially true, in case when testing team has time to test all the requirements. In that case its being use for to just prioritization. So that high risk items can be tested earlier.
But when testing team don’t have much time to test all the requirements then Risk based testing is used to test only high risk items, low priority requirements can be tested based on the time left.
Regards,
Tarun Waia