In this phase, we need to look at the type of test cases that are designed for the AUT and devices in scope. Since by this stage the tool and approach are generally identified, we need to focus only on the identification of test cases that need to be automated. During the tool identification application technology, support is verified and a tool that supports the majority of application controls is identified. However, there may still be some scenarios, such as interruption test cases or some specific controls, that are not feasible to automate, or test cases that can only executed one time so cannot be repeatedly executed, such as device activation over SMS. So, in this phase, such test cases are identified and removed from the automation-feasible suite.

The following parameters need to be considered while performing the automation feasibility analysis. This list can be adapted by the project under consideration; however, these are the most commonly used...