What Is Boundary Value Testing?

by Nataliia Vasylyna | February 19, 2016 12:50 pm

Here is one more technique which may intuitively be performed by the specialists from software testing company. It is the method of boundary value checking.

Boundary value testing[1] is closely connected with equivalence class testing which is the basic software testing[2] type. The second core technique used for performing product checking is boundary value testing.

The boundaries of every equivalent class require a special attention. The matter is that the result of inputting the data combination that equals the end of one class and the beginning of the other one can be different. To test such inputs, a specialist should use the requirements.

Usually, the edges of equivalent classes contain a lot of bugs. Unskilled tester may intuitively feel that many bugs are hidden at the class boundaries. Experienced specialists know that very well.

Why Are the Class Boundaries Full of Bugs?

• The errors may occur because of the requirements specification. The output of boundary data may not be specified. In such a case, there is a specification bug. The tester should report this bug.
• The second reason is the code. Bug may occur because of the programmer’s fault. He may mix up some signs, for example, less than (<) instead of less than or equal (≤).

As well as equivalent class testing, the method of boundaries value checking is applied during unit testing[3], integration testing, system testing and acceptance testing[4].

Related Posts:

• How to Execute Boundary Value Testing?[5]
• Black Box Test Techniques. Cause-Effect Graphing[6]

Source URL: https://blog.qatestlab.com/2016/02/19/boundary-value-testing/

---