boundary value testing
play

Boundary Value Testing Chapter 5 Introduction Input domain testing - PowerPoint PPT Presentation

Boundary Value Testing Chapter 5 Introduction Input domain testing is the most commonly taught (and perhaps the most commonly used) software testing technique There are a number of approaches to boundary value analysis We will study


  1. Boundary Value Testing Chapter 5

  2. Introduction  Input domain testing is the most commonly taught (and perhaps the most commonly used) software testing technique  There are a number of approaches to boundary value analysis  We will study some of the limitations of domain testing BVT–2

  3. Program view for boundary analysis  What is the view we take of a program for boundary analysis? BVT–3

  4. Program view for boundary analysis – 2  Many programs can be viewed as a function F that maps values from a set A (its domain) to values in another set B (its range)  The input variables of F will have some (possibly unstated) boundaries: F ( x 1 , x 2 ) : A " B a " x 1 " b c " x 2 " d BVT–4

  5. What is BVA?  What is boundary analysis? BVT–5

  6. What is BVA – 2  For each variable, select five values  Min The minimum  Min+ Slightly above the minimum  Nom Nominal  Max– Slightly below the maximum  Max Maximum BVT–6

  7. Rational for BVA  What is the rationale for BVA? BVT–7

  8. Rational for BVA – 2  What is the rationale for BVA?  Errors occur at boundaries because people  Mistake logical relations such as mixing < with ≤  Are off by one in counting  Fence posts and rails BVT–8

  9. Critical assumption  What is the critical assumption made with boundary value testing? BVT–9

  10. Critical assumption  What is the critical assumption made with boundary value testing?  Single Fault Assumption  Failures are rarely the result of the simultaneous occurrence of two (or more) faults BVT–10

  11. Single fault assumption  Based on this assumption  How are test cases selected when multiple variables are involved? BVT–11

  12. Single fault assumption – 2  Generate test cases as such for all i See Figure 5.2  Values of all but one variable x i at nominal  x i assumes the four non-nominal values from the slide Boundary Analysis – 2  One test case with all nominal values  What are the number of test cases? BVT–12

  13. Single fault assumption – 3  Generate test cases as such for all i See Figure 5.2  Values of all but one variable x i at nominal  x i assumes the four non-nominal values from the slide Boundary Analysis – 2  One test case with all nominal values  What are the number of test cases?  #Variables * 4 + 1 BVT–13

  14. Two-variable function test cases Redundant tests <x 1nom , x 2min > <x 1min , x 2nom > <x 1nom , x 2min+ > <x 1min+ , x 2nom > <x 1nom , x 2nom > <x 1nom , x 2nom > <x 1nom , x 2max- > <x 1max- , x 2nom > <x 1nom , x 2max > <x 1max , x 2nom > Apply BVA to the Triangle problem 1 ≤ a ≤ 200 1 ≤ b ≤ 200 1 ≤ c ≤ 200 BVT–14

  15. Advantages  When does boundary value analysis work well? BVT–15

  16. Advantages – 2  Independent variables  Single fault assumption  Physical quantities  Languages that are not strongly typed  Why were strongly typed languages developed? BVT–16

  17. Advantages – 3  Independent variables  Single fault assumption  Physical quantities  Languages that are not strongly typed  Why were strongly typed languages developed?  To prevent errors easily found with BVA BVT–17

  18. Limitations  What are the limitations of boundary value analysis? BVT–18

  19. Limitations – 2  Does not work well for Boolean variables  Why are these not suitable?  Does not work well for logical variables  PIN, transaction type  Why are these not suitable?  When variables are not independent – i.e. are dependent  What example does the textbook give?  Not that useful for strongly-typed languages BVT–19

  20. Variations of boundary value analysis  What extensions or variations are made for boundary value analysis?  What is the justification for each? BVT–20

  21. Extensions  Robustness testing  Worst case testing  Robust worst case testing  Special value testing  Random testing BVT–21

  22. Robustness testing  What is robustness testing? BVT–22

  23. Robustness testing – 2 Add two more values per variable  See Figure 5.3 Max+ Slightly greater than the maximum  Min– Slightly less than the minimum  What is the expected output?  Hopefully error message, system recovers  Implementing these test cases may not be possible  What is the difficulty?  BVT–23

  24. Robustness testing – 3 Add two more values per variable  See Figure 5.3 Max+ Slightly greater than the maximum  Min– Slightly less than the minimum  What is the expected output?  Hopefully error message, system recovers  Implementing these test cases may not be possible  What is the difficulty?   Determining the expected output for out of range values BVT–24

  25. Robustness testing – 4 What are the number of test cases?  When is robust testing mandated?  BVT–25

  26. Robustness testing – 5 What are the number of test cases?  #variables * 6 + 1  When is robust testing mandated?  With exception handling  BVT–26

  27. Worst case testing  What is worst case testing? BVT–27

  28. Worst-Case Testing – 2  Rejects the simple fault assumption and tests all combinations of values  Often leads to a large number of test cases with low bug-finding power See Figure 5.4  Why?  What are the number of test cases? BVT–28

  29. Worst-Case Testing – 3  Rejects the simple fault assumption and tests all combinations of values See Figure 5.4  Often leads to a large number of test cases with low bug-finding power  Why?  Typically there are few bugs compared to the number of tests  What are the number of test cases?  5 ^ #variables BVT–29

  30. Worst-Case Testing – 4  What type of testing is better to do in place of worst case testing? BVT–30

  31. Worst-Case Testing – 5  What type of testing is better to do in place of worst case testing?  Often better to use Special Value Testing BVT–31

  32. Robust worst case testing  What is robust worst case testing? BVT–32

  33. Robust worst case testing – 2  Add the values min– and max+ to the possible variable values See Figure 5.5  Now take all combinations of variable values  What are the number of test cases? BVT–33

  34. Special value testing  What is special value testing? BVT–34

  35. Special value testing – 2  Use best engineering judgment  Intuition  Domain knowledge  Experience  Soft spots BVT–35

  36. In class activity Do exercises 1, 2 and 3  BVT–36

  37. Random testing  Select random values for each variable  How many tests do we make? BVT–37

  38. Random testing – 2  Select random values for each variable  How many tests do we make?  Related to the probability of producing every outcome at least once  Related to the probability of executing every statement / path at least once BVT–38

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend