Test design techniques — Boundary value analysis and Equivalence partitioning

The fastest way to test input fields are a test deign techniques — boundary value analysis and equivalence partitioning. Father we will explain how those techniques work and why we need to execute them.

Equivalence partitioning

equivalent-partitioning

Equivalence partition — means that the inputs and outputs of the component under test can be partitioned into ordered sets with identifiable boundaries. The values in the same set will be treated in the same way, that’s why we need to check only one value to know the result of testing the whole equivalence class.

For example:

You have the input field when you enter the site. There you must type your age. SRS says that when the user is under 18 he isn’t allowed to enter the site and no other information. We can divide all inputs in to ordered sets (equivalence classes). They will be from 0 till 18 and from 19 till for example 120 years. We also can use a negative testing and use equivalence classes from — ∞ (infinity) to -1 and from 121 to + ∞ (infinity).

When we know all possible equivalence classes we need to check their boundaries, because a lot of bugs appear in this place and, as you know, the earlier bug was found the chipper it is for the company.

To know the result of testing in this equivalence classes we need to check such inputs: -2, 10, 45, 122. This type of testing is called equivalence partitioning.

 

Boundary value analysis

boundary-value-analysis-2

Boundary value analysis — is made for testing the inputs and outputs behavior on the boundaries and outside of them in the equivalence classes.

For example:

We will take the example that was earlier with a site and an input field. To know the behavior of the program on the boundaries we need to check them out and the values outside them.

That is why we need to check such values for valid equivalence classes:

  • -1, 0, 1
  • 17, 18, 19
  • 18, 19, 20
  • 119, 120, 121

If our test show that the boundaries work correctly to requirements we can move farther with testing other functionality.

Похожие публикации (Realted posts)
Black box/ white box/ gray box testing simple expl... If you want to know approaches to testing software depending on access to source code, than you're in the right place. Were going to give a simple exp...
Smoke & Sanity testing — what is it and... When we are talking about smoke testing we're assuming that it's the first test you need to do when you'll have a new build to test. Smoke testing ...
Regression testing — what is it in software ... Regression testing is a testing of an old functionalality for corect work after there were some fixes or features addited. It is done to make sure tha...
Levels of software testing — 4 testing level... As a future or present software tester you need to know the theoretical aspects of a testing. Now were going to describe 4 testing levels which you ne...
Software Development Life Cycle (SDLC) simple expl... If you want to build a good and quality software product you need clearly understand the software development life cycle. Starting with gathering requ...

Добавить комментарий

Ваш e-mail не будет опубликован. Обязательные поля помечены *

1 × пять =

Проверка комментариев включена. Прежде чем Ваши комментарии будут опубликованы пройдет какое-то время.