What is Equivalence Partitioning? - Testing

What is Equivalence Partitioning?

Equivalence Partitioning (EP) is the process of methodically reducing the huge set of possible test cases into a much smaller but still equally effective set. The goal of EP is to reduce the set of possible test cases into a smaller, manageable set that still adequately tests the software. Since we are choosing not to test everything, we are taking on risk. So we need to be careful how to choose classes. Also note that EP is a set of test cases that test the same thing or reveal the same bug.

Example: If a students MarkSheet s/w takes numbers only from 0 to 100, we need to check that the system takes all the numbers between 0 and 100 (including both) and it does not take any other number. Now if we have to verify this, ideally we need to make sure system accepts all numbers from 0 to 100 and it does not accept any number <0 and > 100. Testing all these numbers is practically impossible because we cant test for all number from 0 to -8 and from 101 to +8. So we could partition the i/p data into 2 classes: Valid and Invalid. Where valid class would include all the numbers between 0 to 100 (including both) and invalid class would include numbers <0 and > 100. Thus, we can test for few entries from both the classes and safely say that the s/w works for all the numbers.

The input data is divided into partitions and values are chosen from each partition from which the test cases are derived to perform the test.

Example: if the valid range is 1 – 12, then this is known as a partition and the invalid partitions would be values <=0 and values >=13.
Concept of Decision Tables - Testing
Concept of Decision Tables - Decision tables models the complicated logic into compact and precise way. Decision tables are associated with conditions and their subsequent actions to perform.........
Explain how to define Severity Rating in your project - Testing
Severity Rating in your project - Severity rating is a combination of three factors: - The frequency of the problem occurrence. It could be common / rare - The impact of the problem. It might be easy or difficult for overcoming of users - The persistence of the problem. It might be a one time problem or could repeatedly be occurring.........
Testing - What is boundary value analysis?
What is boundary value analysis? - Test cases written for boundary value analysis are to detect errors or bugs which are likely to arise while testing for ranges of values at boundaries..........
Post your comment