Your SlideShare is downloading. ×
Robust Test Design - a mindmap
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Robust Test Design - a mindmap


Published on

This mind map was presented at HBT Master Class, Aug 9, 2012.

This mind map was presented at HBT Master Class, Aug 9, 2012.

Published in: Education

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Are my test cases adequate? Challenges Do I have the least number of test cases? What "fishes" to catch? i.e PDT to look for Where to "fish"? i.e What Req, Feature, Component? HOW? Fishing Adopt a What kind of net? SCIENTIFIC analogy APPROACH i.e. What test techniques? Objective: Catch fishes that matter, efficiently How to cover quickly? What tools and what TS? Testing-Scientific Approach Are the expectations of Cleanliness criteria end-users "Business goal" Potential Defect Types Classes of defects that may be probable (PDT) "Technical goal" Unit testing Integration Test levels testing 1. Choose quality level. System Quality levels testingDescriptive NOT Test levels 2. Identify conditions Clear notion of to pertaining to the level. "HOW CLEAN"Prescriptive Quality NINE levels 3. Generate scenarios. levels Each level focused on uncovered 4. For each scenario, certain PDTs generate data values Access control for each input. Design test 5. Combine the data process Input validation optimally to generate test test cases. Interface validation test 6. Trace the Interaction test scenarios/cases to PDTs and ensure that Structure test the PDTs pertaining to Good citizen that level are test uncoverable. Functionality test Robust Test Design Load, Stress Test types test Powered by HBT Installation test Performance test Compatilibity Properties of test good TS/TC Scalability test Objective Migration test Pre-requisites Volume test Usability test Execution steps Documentation Security test Data set(s) to be used End-to-End Expected outcome Concepts operations test Enables design of QL-CC-TT TS/TC mapping "EXTERNAL" Behaviour based Classification based on PROPERTY "INTERNAL" Structure based Test techniques Scenario generation Design Classification based on Data generation techniques OUTCOME STEM Core Concept "Techniques landscape" Test case generation Is a flow Represents a behaviour Behaviour emanating from a combination of conditions Positive - Correct use scenario Test scenario Negative - Abuse scenario Scenario is what is automated Is a collection of test cases #TS governed by #conditions Is a "stimulus" To excite the ... to invoke a SUT behaviour All data values valid Positive Test case Is always part of +ve TS At least on data value Negative invalid Is always part of -ve TS Requirements traceability Adequacy Fault traceability Code coverage