Skills That Help You Transition From an Automation Tester to a Key Enabler in Automation Testing
In today’s agile and quality engineering driven software development world, QA & testing divisions are trying to make QA process faster and even more productive & effective. Automation testing turns out to be one such method which can accelerate your overall QA process and bring in more time to test functionalities than testing same functionality across various scenarios.
So every time a new project pops up, the 1st reaction of every tester is to find an opportunity to implement automation testing. However, test automation strategy is usually discarded by project managers or clients if the duration of the project is small or if they don’t have an idea for how long the project will continue. In such scenarios, it becomes very difficult to convince your project managers or clients why Automation testing can still be of value.
In this blog I have tried to point out few skills & guidelines which can help you overcome this challenge and become a key enabler in automation testing team rather just a automation tester. Using these guidelines you can burst few myths about automation testing such as, that
- It can only be used for long term projects
- Investment for Automation is too high
- ROI is very less for automation
While we discuss at length how automation testing can be leveraged for short term projects or project where duration is not capped, use of open source tools and structured framework can bring down your cost considerably.
Here’s the checklist of skills Automation tester should have –
- Since QA teams might work on multiple projects at the same time, automating all features or spending a lot of time in designing the test framework is not going to help the QA team or the client.
- Choose what types of automation you will use. Projects where UI and API development is involved make sure you build your case around these types of automation 1st.
- Rather than designing a framework from scratch, use frameworks which are easy to implement and prepare a working demo for basic test cases, keep in mind to use open source tools. As clients may not be aware of automation benefits so keep highlighting the benefits and add features which are quite helpful for the clients.
- Prepare a small video of automation execution and log time from start to end, then send a report comparing time difference in manual and automation.
- Use an open source tool like Jenkins to create a pipeline and add automation projects to it
- Reporting of automation suite should be presentable and if possible add a trigger email notification for client post execution.
- Engage with the development team to get inputs.
- Make the automation scripts easy to understand and with proper structural flow
- Identify areas where test automation can be applied:
- You can introduce automation testing for code check-in and see if the new code does not break the system
- Use automation scripts where same functionality needs to be tested across various configurations.
- Projects where large amount of data sets needs to be tested, automation becomes your safest bet
- If the project is in agile methodology, there is no time to conduct regression testing manually within one sprint. In such scenarios, automation will be very helpful
- Make use of free tools and frameworks to bring down the cost. Here are few examples of tools you can use.
|Selenium Webdriver||It is an open source browser automation library.
To know more: https://www.selenium.dev/
|Maven||It is an open source Dependency management tool which is used to design framework.
To know more : https://maven.apache.org/
|TestNG||It is an open source testing framework inspired by Junit and Nunit.
To know more – https://testng.org/doc/
|ExtentReporting||It helps to design interactive, detailed reports, and it is also open source.
To know more – https://extentreports.com/
|Jenkins||To implement CI/CD and integrate automation framework Jenkins can be used.
To know more – https://jenkins.io/
While you keep in mind all the above factors for creating business case for test automation, prepare a robust POC to showcase how automation is going to make the build process smooth and errorless. Hope the above guidelines help all the Automation Testers/SDET/Engineers to crave their path towards an Enabler.
Sidharth Shukla | Lead Software Engineer
Sidharth Shukla is an Lead Software Engineer at GS Lab and has expertise in different types of testing including Functional, Automation, and Performance. Currently he is working on UI and API automation with the implementation of CI/CD for Automation Projects. He has a good exposure to designing the framework for UI/API automation from scratch and mapping it with the deployment lifecycle.