A well-designed test case contains one or more clearly defined expected results and clearly defined success / failure criteria for any type of testing. Usually the expected results and success / failure test criteria are closely related. If the expected result or some set of expected results is obtained when the system is transferred from one given state to another, then the test case passes. If the expected results cannot be recorded after performing the specified actions, the test does not pass. For example, suppose that a zip code value is entered in the data entry field, and it is expected that the name of the relevant state will be displayed after clicking the “Specify staff” button. If after entering a set of zip codes the correct state name appears for each of them, it means that the test gets the expected results and therefore passes. If, however, when you enter Seattle’s postal code, Florida is displayed on the screen, you may consider that you were lucky that you had found a defect, since the expected result was not obtained.
If you are well aware of benefits of using outsourced pen testing service then you will become our client! We are reputed qa and testing specialists who live in Ukraine but help people all over the world to create high-quality IT products. Based on our huge experience in software testing industry we perform an authorized simulated attack on a PC to evaluate security of the system. In so doing, we manage to identify potential weaknesses as well as the potential for hackers to access the system’s features and other sensitive information.
It is worth mentioning at least one additional characteristic of a well-designed test case – it should not be redundant. An optimal test schedule requires that you perform as much testing as necessary to detect all faults before delivering the software to the customer, but you should not waste time running redundant tests.
Summarizing, it can be argued that the following characteristics should be associated with the test case:
- It must have a high probability of detecting a defect.
- It must be reproducible.
- It must have clearly defined expected results and success / failure test criteria.
- It should not be redundant.
As soon as the test plan document is ready, it should be checked in the context of the related materials:
- the requirements definition document (technical information);
- the test input and test configuration.
This check is aimed at verifying the following:
- The test plan document under consideration covers all technical requirements. If a particular requirement is not tested, a RTM matrix or test plan document should contain a record explaining why the corresponding requirement is not covered by the test.
- Each test case is supported by the appropriate input data.
- There is a suitable configuration for each test case, and these configurations are not redundant.
- The test plan document serves as the basis for developing a detailed testing methodology.
As a result of the revision, tests can be distributed among participants of the test group for further detail.
Add Comment