2.1.2.Semi Automated Testing
When we automate tests, we often find that there are cases that require manual intervention to decide the success/failure of a test case. There is still a place for manual testing with tool assistance in our projects. Semi automated tests falls in between the fully-automated tests and manual tests. We use the tool to perform operations that can be automated, leaving the some of the verification process to the manual tester.
Test Cases that can be semi automated
- Look and Feel
We often need to check the look and feel of an application. We can use automation to ensure that we reach each of the application windows and perform actual verification manually.
- Checking for Organizational Standards
Similar to the Look and Feel tests, we may want to check whether the UI is following our organizational standards. In MarathonITE we can create a checklist listing our standard and then use semi automated tests to insert the checklist to create our report.
- Non deterministic output
When the output from our test case is non-deterministic, it is almost impossible to create a automated test. Semi automatic tests can be used in these cases.
Avoid these cases
- Synchronizing between two applications
There are cases where our test depends on the output from another application. It is still better to automate the whole test (though difficult), than keeping it semi automated.
- Processing output from the application
In cases you need to operate on the output of the AUT to decide the status of a test script, it is better to automate the test.