12-Apr-2018
Introduction to Automated Testing Life-Cycle Methodology
By Harinder Kaur
12-Apr-2018
By Harinder Kaur
Automated Testing Life-cycle Methodology is the process of testing which is executed in planned and a systematic manner. In this process, different activities are carried out to improve the quality of the product. It is best to increase the efficiency, coverage, and effectiveness of your software testing.
Let’s see what all stages are involved in it:
Before we start to automate the manual test cases, firstly we need to verify that the test cases are feasible to automate or not. On the basis of the feasibility study, we can give accurate estimates, so a feasibility study must be done. Let’s take an example: An automation team has given an estimate to the client and started to automate the test cases without analyze it. During automate the functionality they facing some issues like in one test case client want to submit a form with a captcha but they are unable to automate a captcha or various types of issues.
Now you need to discuss it with your client, at that time it will leave a bad impression on the client. Here the first question of the client is “Why did not analyze it in the first phase?” I think now you understand the importance of a feasibility study. There must be a checklist for a feasibility study by using it we decide the automation:
i) Walkthrough of Software
ii) Client requirement for automation
iii) Development and stability status of the application
iv) Categorizing the test cases (Smoke/Regression)
v) Automation Percentage
vi) Return on investment
[ Related Read: Test Automation ROI ]
TA = Time taken for automation testing
TM = Time taken for manual testing
TS = Time saved due to test automation
TS = TM-TA
Investment:
CHS = Cost of hardware and software
CT = Cost of training staff on automation
CDM = Cost of development and maintenance of script
CA = Cost of Automation
CA = CT+CDM+CHS
The formula of Return on Investment = Benefits from automation over manual / Cost of automation over manual
This phase contains what, when and how to automate the test cases. We can plan it in a well-organized manner only if we study the feasibility of the test cases category (Smoke and Regression). In this phase we can plan for:
i) The architecture of the automation framework
ii) Effort estimation to automate the test cases
iii) Automation resources allocation
iv) In-Scope and out of scope items
v) Scheduling and Timelines
vi) Automation tool
vii) Test data
In the test plan, we can also consider the limitations, risks, and dependency of the automation over the application. After preparing the automation plan, it is shared with the client for review and approval.
In this phase, we set up the machine or remote machine in which we develop or execute the test cases. In this, we can mention hardware and software requirements, necessary machines. We need to set up a separate instance of the application as there must be no disturbance during the development and execution of the scripts. In this phase, we also set up an automation testing framework according to the application requirements.
Once the automation framework is set up, testers start automating the test cases according to the plan. In this, we create common functions that can be reused in further scripts. Developed scripts should be easy to understand, well structured and documented in case of peer review or client understanding. Use the process of reporting that is easy to understand and contains screenshots when the test scripts fail.
The script should be created as per the code standard and the code should be optimized. The assertions must be used in all the test scripts. Make sure that in this phase all the test cases get automated and run independently.
In this phase, we perform the actual execution of all automated scripts and analyze the result. Make sure that created scripts are stable to run in multiple environments and multiple browsers (as per the client’s requirements). All the created scripts must be executed in this phase. In case, any failure occurs during execution then it should take the screenshot for the same. One can also create a batch file to execute the scripts as it will save time and effort. Test management and continuous integration tools must be integrated within the script which invokes the test automation tool. By using these tools, execution can be done overnight to save time.
Check out top automation testing tools for desktop applications
In this phase, we gather the test automation result and share the result with the team, stakeholders and client. Test results must be easy to understand for everyone involved. Proper filters must be used in the report. You should have a good report like TestNG, Extent Report, etc.
This is a continuous improvement process phase. In this phase, test cases are updated regularly as per the functional or UI changes. In this, we can also automate new test cases that were not included during the planning phase. Effort estimations, scheduling and timelines are also set for this phase.
Harinder Kaur
Harinder works as Automation Test Engineer at BugRaptors. She is experts in writing scripts in web driver/Behat using Cucumber, gherkin languages. She has tested the web application on multiple Browsers and OS using Automation.
Interested to share your
Read More
BugRaptors is one of the best software testing companies headquartered in India and the US, which is committed to catering to the diverse QA needs of any business. We are one of the fastest-growing QA companies; striving to deliver technology-oriented QA services, worldwide. BugRaptors is a team of 200+ ISTQB-certified testers, along with ISO 9001:2018 and ISO 27001 certifications.
Corporate Office - USA
5858 Horton Street, Suite 101, Emeryville, CA 94608, United States
+1
(510) 371-9104
Test Labs - India
2nd Floor, C-136, Industrial Area, Phase - 8, Mohali -160071, Punjab, India
+91 77173-00289
Corporate Office - India
52, First Floor, Sec-71, Mohali, PB 160071,India
United Kingdom
97 Hackney Rd London E2 8ET
Australia
Suite 4004, 11 Hassal St Parramatta NSW 2150
