Test Scope Redux

404 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
404
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Test Scope Redux

  1. 1. Test Scope ReduxThinking about what not to test
  2. 2. Introduction There are many ways to go about setting a test scope for a test activity We are trying to cover as much of the complete “test space” as possible constrained by a number of factors; time, tools, budget, business decisions, optimizing resource utilization and so on We can never test everything – cover the entire “test space” – there is always some constraint stopping us from achieving this We are trying to be as efficient and effective as possible, and to minimize risk given a set of constraints
  3. 3. Traditional Scope Setting Overview Quality Model [1] Known Risks Technical Scope Setting Test Scope Information Historical Data Other factors Constraints
  4. 4. Traditional Scope Test Space Test Scope
  5. 5. Test Scope Redux One way to work with setting the test scope is to turn things around Don’t start thinking about what to test – start thinking about what NOT to test Once you have narrowed down the test space, it is easier to set a scope that is as effective and efficient as possible We will never know what the complete test space looks like – but this way we can at least try to narrow down the field
  6. 6. Scope Setting ReduxQuality Model [1] Known Risks Technical Scope Setting Excluded Test Space Test Scope InformationHistorical Data Other factors Constraints
  7. 7. Test Scope Redux Test Space Excluded Test Space Test Scope Excluded Test Space
  8. 8. Stakeholder Communication Another benefit with using this approach is that stakeholder communication can become clearer The stakeholders will know in more detail what you are excluding from the test scope – not just a list of areas that will be tested, but a clear statement of what will NOT be tested as well
  9. 9. Conclusion This is one additional way of thinking when setting a test scope By turning things around it is possible that the tester sees risks and problems that may otherwise be overlooked By narrowing down the test space by excluding parts of it, it can become easier to set an efficient and effective test scope, as well as clearly communicating this scope to stakeholders There are many other ways to set a test scope – by using several different approaches we can continuously improve
  10. 10. References [1] IEC 9126http://en.wikipedia.org/wiki/ISO/IEC_9126

×