Boundary Value Testing Southrn Polytechnic State 边界值测试南方州立理工.pptVIP

Boundary Value Testing A type of “Black box” functional testing The program is viewed as a mathematical “function” The program takes inputs and maps some out-puts The internal of the program itself is not considered 2. A technique to generate test cases via considering the inputs to the program (sometimes the outputs) 3. The rationale for this focus is that there are experiences from the past which indicate that errors tend to occur at the “extreme” points (especially of inputs). Input data Loop iteration Output fields Recall this Is a special relation A simple example Consider a program that reads the “age” of students in SWE 3643 and computes the average student age of the class. input (s) → Program → output: average age What type of test data would you input to test this program? Input (s) to Program Average First question would be - - - how many inputs should we input? The answer should be some integer n 0 , but should be 2 or more? (what about 0 input ? does that work for “average”) Second question would be- - - what value should each input age be? Try some typical age such as 23, 45 or 4 Try some atypical age 125 or 700 How about trying a “wrong” age of -5 or 0 When we try the atypical age or some wrong age, we may discover that the program may not “handle” or process properly possibly resulting in a failure or and incident of failure. (Failure in this case, may include strange answer, but not necessarily program termination.) Example: Program Average Number of input data, n 0. We pick the lower bound is n = 1 How big can n be ? Can n be 1,000,000? (assume, yes) Our input test case should include only one input, n = 1 Our input test case should include n = 1,000,000 inputs So 1 and 1000000 are the lower and upper boundaries of the number of inputs, respectively. How would the program perform with no data (n=0) or 2,000,500 pieces of inputs? Age Inputs: composed of only typical ages Look at the output,