It is very difficult to check every possible condition or scenario in the software application. Software Test case techniques help testers write an efficient test case with the maximum possibility of finding a defect in software. These are the most frequent Test Case Design Techniques used,
Boundary Value Analysis (BVA):
Boundary value analysis testing is the process of testing between boundaries between or partitions of the input values. So these extreme ends like Start-End, Lower-Eupper, Maximum-Minimum, and Just Inside-Just Outside values are called boundary values and the testing is called "boundary value analysis testing". The basic idea in normal boundary value testing is to select input variable values of :
> Minimum value
> Just above the minimum value
> A nominal value
> Just below the maximum value
> Maximum value
Equivalence Partition (EP):
In this technique, values or data are divided into two divisions: Valid Values and Invalid Values. This kind of black-box testing is applied at all levels of software testing like Unit, Integration, system, etc.
It divides the input data into various equivalence data classes. One can opt for this kind of technique where there is a range of input fields available. Boundary Value Analysis exists after the implementation of Equivalence Class Partitioning.
Negative Testing
In this type where the tester enters invalid data or unexpected input to verify the response of the software. For example, testing the Login function by entering an invalid UserID or Password. We can check Negative scenarios by entering Invalid credentials, uploading files other than those mentioned, uploading images more than the size mentioned, entering invalid phone numbers and characters, etc. It gives certainty to almost 0 vulnerabilities. It gives more confidence before going live and surety to cover almost all test cases.
Edge Cases
An incident where the tester examines either the beginning or the end of a range, but not the middle, is called an edge case. Such types of test cases cover almost the extreme ends of the range.
When you key in the employee information, the maximum age limit would be 70 or 80. But if you key in a year that results in employee age as more than 200, the software will not function correctly. This error should be caught while doing edge case testing. Even if we release this product to the client without testing this case, it will continue to work until the user intentionally enters the age above 200
State Transition Technique:
This method is used when software behavior changes from one state to another following a particular action.
Error Guessing Technique: This is guessing/anticipating the error that may arise while doing manual testing.