Following are few key points to check test case eligibility criteria/feasibility analysis for automation.
Test Case Eligibility Criteria For Automation | |
Category | Parameters |
Test Case/Scenario Structure | Test Case should be well documented with |
- Defined test data | |
- Prerequisites Documented | |
- Clear pre and post conditions should be clearly defined or highlighted for individual steps | |
Test Tool Feasibility | Application objects ranging all the navigational pages across the test flow should be identified by the underline automation tool |
System/Test flow | Test case should not contain steps that execute that involve partial execution of few steps and then wait for the system refresh for undefined hrs and continue once the system is refreshed with the required data. |
These type of test cases fall under partial automation criteria and once automated these test cannot be executed in an unattended way, as the refresh time is not defined | |
3rd party application integration | In case the test case integrates with any 3rd party application, then it would be recommended to check the data flow between these system to ensure seamless execution of the automated tests. |
Test Case Complexity | Test case tending to be too complex with respect to automation and having limited execution cycles are not recommended for automation. |
Hardware Interaction | In case the test case interacts with an external interface, feasibility of the interface is considered while prioritizing the test case for automation, depending on the availability |
Cross Browser Testing | UFT supports IE, Chrome, Mozilla with limited versions. If there are any test cases for automation to execute on multiple browsers then we have to evalute those browsers with versions |
Non Functional Testing - Verifying web page content with alignment, format, auto numbering, paragraphs..etc | Not good candiate for Automation |
Automation Testing in a Multi-Country / Multi-Lingual Deployment(localization testing) | More effort required to create scripts to adopt locatization(multi-lingual) testing. PoC is required to evalute this |
No comments:
Post a Comment