1 / 13

Risk Based Testing - Revisited

Risk Based Testing - Revisited. Sreeram Kishore Chavali 9 July 2002. Agenda. Examples of Risks Customizing test plan template Discussion and Q&A. Business Risks. System forces user to spend more time than he feels appropriate System Crashes resulting in loss of business Corrupts data

petra
Télécharger la présentation

Risk Based Testing - Revisited

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Risk Based Testing - Revisited Sreeram Kishore Chavali 9 July 2002

  2. Agenda • Examples of Risks • Customizing test plan template • Discussion and Q&A

  3. Business Risks • System forces user to spend more time than he feels appropriate • System Crashes resulting in loss of business • Corrupts data • Delivers slow performance • Incorrect Documentation

  4. Software Bugs – Risks Examples • Risk Level 5: • System crashes • Cannot Enter Data • Loss of Data • Inconsistent Data accepted • Invalid data accepted • System becomes unusable • Mostly Positive Test Cases fall under this Risk Level. 100% chances of user facing this scenario

  5. Software Bugs – Risks Examples • Risk Level 4 • Test Scenarios that are not always encountered • System does not work properly at boundary conditions • Invalid data and invalid states of application • System is usable but causes sporadic problem and gives an impression of being unstable and incomplete • > 50% chances of user encountering this scenario

  6. Software Bugs – Risks Examples • Risk Level 3 • Mostly negative test cases • Cause application to behave incorrectly • Chances of user encountering this scenario is less probability • < 30% possibility of user encountering this situation • Application is usable and working

  7. Software Bugs – Risks Examples • Risk Level 2 • Any test scenario with less than 10% probability of user encountering this scenario • Application behavior not consistent but there are workarounds • Acceptable discrepancies

  8. Software Bugs – Risks Examples • Risk Level 1 • Remote GUI Defects: Accelerator not working in a not so frequently used dialog • Almost 0% probability of user finding the problem • Even if user finds the problem, it is something user would not worry about reporting this issue.

  9. Risk Matrix

  10. Test Plan Vs Test Execution • Test Plan enables us to explain test scenario, assumptions, scope and other details • Needed in a paragraph format • Use Word format to specify • Will consists of set of cases • Cannot be used in metrics • Not changed frequently • Test Case: A case independent of test scenario with a defined expected outcome • Atomic entity • Can be used in metrics • Can be changed or removed

  11. Customize the Template to suit needs • Customize Template to make it usable • Still Achieve Basic objectives • One Sheet of all test cases • Easy to filter, report and monitor • Easy to add/modify case details and status

  12. Realizing Benefits with Risk based test cases and Excel Sheet format • Test Execution by Risk • Quantifying progress • Understand Test Progress and dynamics of developments • Concurrent update of Status • Continuous addition/modification/deletion of cases

  13. Thank You

More Related