Equivalence partitioning test technique is commonly connected to the inputs of a tested component, although in some separated cases it can be utilized on the outputs of components in the product application.
Equivalence partitioning test design technique uses a subset of information which is illustrative of a bigger class.
The testing techniques equivalence partitioning includes partition testing of the input domain of a software system into a few equal classes in a way that the testing of one specific representative from a class is identical to the testing of some different value from the subject class. As it is basically unrealistic to do testing so thoroughly, the other better option is to confirm to check in the matter of whether the program treats specific input bunches in a similar way or not.
If some set of like values is available in the input sphere, at that point such values can be dealt with as a single equal class and any single representative out of them can be tested. Equivalence partitioning test technique is executed as an alternative for doing comprehensive testing for each value of information in a bigger class.
What is Equivalence Partitioning Testing?
Equivalence partitioning test technique also called as equivalence class partitioning testing technique. It is abbreviated as ECP. It is a software testing techniques that partitions the input test information of the application under test into each partition at least once of proportionate information from which test cases can be derived.
A benefit of this approach is it decreases the time required for performing testing of a product because of less number of equivalence partitioning test cases.
Equivalence partitioning in black box testing means to decrease the number of repetitive test cases by taking out those that create a similar output and don’t really uncover defects in program functionality.
Equivalence partitioning example:
E.g.: If you are trying for an input box tolerating numbers from 1 to 1000 at that point there is no utilization in composing a thousand test cases for all of the 1000 valid input numbers in addition to other tests cases for invalid information.
Utilizing equivalence partitioning test technique above test case design can be partitioned into three sets of input data called as classes. Each test case is a delegate of a particular class.
So in above example, we can be partitioned our test cases into three equivalence classes of some invalid and valid inputs.
1) One input data class with all valid inputs. Pick a single value analysis from extending 1 to 1000 as a valid test case. If you select different values in the vicinity of 1 and 1000 the outcome will be same. So one test case for valid input information should be adequate.
2) Input information class with all values underneath as far as possible. I.e. any value beneath 1, as an invalid input information test case.
3) Input information with any value more prominent than 1000 to speak to third invalid input class.
So utilizing equivalence partitioning test technique you have arranged all conceivable test cases into three classes. Test cases with different values from any class should give you a similar outcome.
We have chosen one representative from each input class to outline our test cases. Test cases values are chosen such that biggest number of properties of equivalence class can be worked out.
Equivalence partitioning test case design techniques utilize least test cases to cover most extreme necessities.
Recent Comments