Approach to Automation Testing Framework
Identify test scope:
Considering the
organization's requirements, test automation activities can be performed with different
scopes. It can be project specific/Enterprise Specific/Product Specific.
Identify Testing Needs and Automation Need:
Testing requirements and their nature is studied for the
product/application/modules. Each requirement has its own actions, validations
for testing. Identify if there is a need for automation and will be useful
in a long run. There are several points to be kept in mind while automating any
application.
Identify Tools:
Next task would be identifying different industry-standard
tools based on the requirements. This can also include tools to be purchased or
open source tools. Identified tools must be evaluated against the checklist. Rate and Select Tools - Based on the sample
run, supportive tools could be identified and rated. Also there may be
scenarios, where multiple tools satisfy the requirements. In the said scenario,
we may need to choose more than one tool, for test automation.
Automation feasibility :
Every tool has its own limitations. A feasibility study
needs to be conducted for the requirements against the tools. This study would
result in listing requirements that can be automated. Also based on the nature
of the requirements, automation feasibility needs to be identified.
Which Test Cases to Automate?
a)
High Risk - Business Critical test cases
b)
Test cases that are executed repeatedly
c)
Test Cases that are very tedious or difficult to
perform manually
d)
Test Cases which are time consuming
e)
Frequently used by users
The following categories of test cases are not suitable for
automation:
a)
Test Cases that are newly designed and not
executed manually at least once
b)
Test Cases for which the requirements are
changing frequently
c)
Test cases which are executed on ad-hoc basis.
d)
Not used by user very frequently. (One time
configurations)
No comments:
Post a Comment