Performing software testing, the specialists create test cases – a set of actions which are executed for checking a certain feature of the product under test. When comparing the test cases and test scenarios, then the last are more extensive and ensure the coverage of wider functionality.
The test cases should be simple and understandable not only for their author but also for all specialists of software product testing. Sometimes one tester creates cases and the completely different person runs them.
For the test cases, mainly, the assertive applications are typical, for instance, “move to the Main Page”, “click the button”, and etc. Thus, the process of running the test case will be quick and correct.
Performing functional testing, usability checking, performance testing, the specialists create cases, focusing on the end users, namely – on their expectations. At that, all client’s requirements should be met.
It is important not to repeat the same test cases. If one test case execution requires repeating all steps of another one, then it is better to mention this in the preconditions field.
One should not guess the system behavior. When creating test cases, it is always necessary to base on the product specification.
What should each test case include?
- Description of the requirement under test.
- Explanation of the system checking method.
- The test parameters: application version, OS type, software version, access parameters, and so on.
- The expected results.
- Data input and output parameters.
If it is an automated test script, then it is necessary to comment the peculiarities of input data, the objectives of the expected results. Whether it is mobile testing or web application checking, the test cases ensure qualitative checking of diverse systems.