All about the elementary comparison test
Each software has its own unique set of requirements and features that must be tested to ensure that the software works properly. There are many different ways to test software, but a common approach is the elementary comparison test. This can be a valuable way to detect errors in your code. What exactly does this test entail, when do you use it, and how? We answer these questions in this blog. Read on quickly!
Different test design techniques
So there are different types of test techniques all of which have their own purpose and properties. In total, there are no less than eleven of which the elementary comparison test is thus one. To choose the right kind of test, you as softwaretester go over what goal you want to achieve. Then you'll delve deeper and get to work on a testing technique.
Each type of test is different and differs on following factors:
- The supplies needed to run the test
- That which is going to be tested
- The test base: all the documents that state how the software should work
What is an elementary comparison test?
An elementary comparison test (EVT) is a testing technique that allows you to thoroughly and in detail test the functionality of software. The test is performed based on pseudocode or a similar specification containing structured decision points and functional paths.
The purpose of the test is to thoroughly cover the decision points and does not focus on combining functional paths.
Required factors to run the test
When performing an elementary comparison test, certain factors are necessary and required. When detailing the test base, you can use the following checklist to verify that the specifications are present:
- Is the processing described in such a way that the various functional paths can be identified in it?
- Is it clear under which conditions a certain functional path is executed?
- Is the processing unambiguously described including input and output?
- Is processing described for all input items?
The elementary comparison test has 4 generic steps
1. Identify test situations
Is it the case that the test base does not contain any pseudocode? If so, it is important to first work it out in terms of IF..THEN..OTHER..ENDING IF. Each decision point in this pseudocode should be given a unique identifier and the desired coverage should be worked out in a truth table. To ensure and improve readability, the truth table is then written out in logical terms. One may also choose to prepare a test graph to graphically represent the test situations.
2. Create logical test cases.
It is important to create test cases in a logical way. For example, it is important that a test case has a beginning an end and one or more decision points where one test situation is taken. These test situations are then linked together in a matrix to form a test case. Make sure that within a test case there are no test situations that contradict each other.
3. Drawing up physical test cases
During this third step, all variables are given a concrete interpretation.
4. Determining the starting situation
The final step involves determining the initial situation whereby the actions required to obtain the initial situation are named.
Learn more about software testing!
Do you have additional questions about the elementary comparison test? Then feel free to contact us! Or maybe you want to learn more about different software testing techniques?TestLearning offers online courses that will help you develop into a professional! You can use our e-learnings flexibly because you can learn when and where it's convenient for you. View our course offering and find out what we can do for you.
Want to know more about Testlearning?
Would you like to be kept up to date with developments around our test training courses? Then follow us on LinkedIn, sign up for the monthly newsletter or read our blogs!