One of the test methods often employed in software testing involves equivalence classes. Simply put, system input is grouped into classes based on representative input domains. A group is formed based on the same test object behaviour.
Structure input & reduce number of test cases.
The biggest advantages of employing equivalence class testing are that you structure the input domain and reduce your testing effort. By choosing input representatives for larger groups you take a shortcut on your test track to reduce the number of test cases to be tested.
A special instance of testing equivalence classes is the analysis of boundary values.
Equivalence classes from requirements.
We are convinced requirements-based testing is leading the way on the road to efficient testing. To do so, you derive input and corresponding equivalence classes directly from your requirements. If necessary, a class may be divided into smaller sub classes.
Once you select one or more representatives from each class, you can start creating test cases.
TPT facilitates equivalence class testing.
Equivalence class testing as a test method attains multiple test goals. Besides, testing equivalence classes is also required by safety norms stipulated in ISO 26262. TPT facilitates these by automating testing process. This way you know that your system has:
1. Correct functionality
2. Correct functionality of safety mechanisms (ISO 26262)
3. Correct interfacing
4. Correct interoperability
5. Correct response to configuration/ application data
6. Completeness (enough, too much implemented)
Feel free to browse through our Glossary of Test Terms in case you are looking for terminological explanations.