Boundary Value software testing/analysis
This technique says that most errors occur at boundaries. For example, if we have variable marks and the range of variable marks is from 1 to 100 then we can say that we should test them 100 times and one time for each value.
We will test that if marks are 1 then 1 is correctly entertained by our software or not?
We will test that if marks are 2 then 2 is correctly entertained by our software or not?
We will test that if marks are 3 then 3 is correctly entertained by our software or not? And so on for each value of marks.
This is a very exhausting process and wastes a lot of time and budget if we test values of only one variable a hundred times.
The solution to this problem is a simple boundary value testing.
Boundary value testing says that errors mostly occur at boundaries, so we should only test the values at boundaries.
For example, we can test the values at 5 different points like
Here in case of marks, the range of marks is 1 to 100. So if we find these five values then;
Min is the minimum value of the data range.
Min+ is the minimum value +1 among the data range.
Nominal value can be any typical value that is far away from boundaries. For example, here we chose 50 as nominal but we can also choose 51, 52, 53, 49, 48 or any value that is typical value and far away from boundaries. As we see that 50 have a very large distance between 1 and 2. Similarly, 50 have a very large distance against 99 and 100. So 50 can be a nominal value.
Max- is the Maximum value -1 among the data range.
Max is the maximum value of the data range.
We can generate 5 test cases from one variable marks as follows.
Test case # 1: To test 1
Test case # 2: To test 2
Test case # 3: To test 50
Test case # 4: To test 99
Test case # 5: To test 100.