I am leading the manual testing topics of our native mobile application. I have been tasked to give a report to management where we say total manual cases, total automatable cases and total automated.
This way the management can see the progress of automation.
Manual Testing Approach:
We have total of 618 Manual test cases as a singe suite & each case will have a Priority (1 or 2 or 3) associated with it. For Story tests, apart from the newly created story test cases, we also consider all P1+P2+P3 from the particular module which is related to/impacted by the story. End of the release, for regression we consider all P1 cases from all the modules. Only if it is a major release then during regression we consider all P1+P2+P3 from all the modules.
While looking for Automation, I feel that it is not worth to spend time on considering the P2 and P3 cases because of two reasons
- Those will be executed once in blue moon [We do only minor releases 99%]
- Most of them are actually throw away test cases which were created as part of the User Story testing.
What we want to achieve in our Automation?
We want to address the pain areas of QA where some P1 cases need to be tested against 20+ languages and kill the manual testing time.
Since we do not have different suites like Smoke, Regression, etc., we need to give our testers the test cases in the single suite only to identify what is automatable and not. Is it worthwhile to consider the lower priority test cases as well as the high priority test cases?