Boundary software testing

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. Simple Boundary value testing of one variable:. Boundary value testing says that errors mostly occur at boundaries, so we should only test the values at boundaries.

Here in case of marks, the range of marks is 1 to So if we find these five values then;. Boundary Value Analysis is also called range checking. Equivalence partitioning and boundary value analysis BVA are closely related and can be used together at all levels of testing. Skip to content. Equivalence Partitioning Equivalence Partitioning or Equivalence Class Partitioning is type of black box testing technique which can be applied to all levels of software testing like unit, integration, system, etc.

Order Pizza:. Enter Password:. Report a Bug. By using this technique, we could save a lot of testing time and get good test case coverage. The remaining three techniques will be explained in the upcoming articles. BVA is another Black Box Test Design Technique, which is used to find the errors at boundaries of input domain tests the behavior of a program at the input boundaries rather than finding those errors in the centre of input.

So, the basic idea in boundary value testing is to select input variable values at their: minimum, just above the minimum, just below the minimum, a nominal value, just below the maximum, maximum and just above the maximum. That is, for each range, there are two boundaries, the lower boundary start of the range and the upper boundary end of the range and the boundaries are the beginning and end of each valid partition.

We should design test cases which exercise the program functionality at the boundaries, and with values just inside and outside the boundaries. Boundary value analysis is also a part of stress and negative testing. Consider an example where a developer writes code for an amount text field which will accept and transfer values only from to The test engineer checks it by entering 99 into the amount text field and then clicks on the transfer button.

It will show an error message as 99 is an invalid test case, because the boundary values are already set as and Since 99 is less than , the text field will not transfer the amount. The inputs to the software or system are divided into groups that are expected to exhibit similar behavior. Thus, it reduces the number of test cases to a finite list of testable test cases covering maximum possibilities. Example: Suppose the application you are testing accept values in the character limit of 1 — only.

Here, there would be three partitions: one valid partition and two invalid partitions. The expectation is that the text field would handle all inputs with characters, the same way. Rule 1: If input is a range of values, then design test cases for one valid and two invalid values.

This black box testing strategy was introduced after equivalence class partitioning where the partition of classes takes place first followed by a partition at the boundaries. The idea regarding this is cleared from the above statements.

Now, it is time to test what are the possible causes for Boundary value testing. Let us assume the next test case that takes the length of the input name from 8 to 14 characters.

Example 1: Suppose, a printer has to make and deliver printed copies ranging from 1 to So, to apply boundary value testing, the analysis is done on the boundaries, taking the extreme ends.

The maximum value is and the minimum value is 1.