1 / 9

Risk & Requirement Based Testing

Risk & Requirement Based Testing. Iris Pinkster – O’Riordain. Why Test Management?. 85 % of companies have no good test management process, consequences: Test projects inexplicably overrun their time Test projects cost far more than estimated Little insight into quality information system

dpena
Télécharger la présentation

Risk & Requirement Based Testing

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 & Requirement Based Testing Iris Pinkster – O’Riordain

  2. Why Test Management? • 85 % of companies have no good test management process, consequences: • Test projects inexplicably overrun their time • Test projects cost far more than estimated • Little insight into quality information system • Little learning effect in the test organisation • Little success, high costs

  3. Business objectives Test Management Test preparation and execution Ideal position Test Management Business Alignment Reputation Management Insight Control Focus Commitment Standard Repeatable Reliable Maintainable

  4. Test Management Model • Risk & Requirement Based Testing (RRBT) • Preparation and execution • Eight phases • Secure in Test Management File

  5. Product risks versus requirements Matching risks and requirements • A risk, no requirement: • Add requirement (find faults earlier) • Remove risk (don’t test more than necessary) • A requirement, no risk: • Adjust risk list (better coverage of testing) • Remove requirement (don’t develop more than necessary, no “frills”) Requirements Product risks Matching requirements and risks

  6. Priorities product risks: an example Must test If this goes wrong than ... … it has financial consequences for our customer. All customers One customer Should test … it has non-financial consequences for our customer. All customers Should test One customer Could test … it has financial consequences for our department. No workaround Could test Workaround Won’t test … it has non-financial consequences for our department. No workaround Could test Workaround Won’t test

  7. Testing under pressure, the Strategic Test Slicing Method (STSM) OUCH!! • Must test: • … • … • … • … • Should test: • … • … • … • … • … • ... • Could test: • … • … • … • … • Won’t test: • … • …

  8. Risk & Requirement Based Testing • Basis for executing test projects • Identify product risks and their priorities • Match with requirements for completeness, but risks are guiding • The most important is tested first • Excellent way of communicating with the business

  9. More information Questions?

More Related