Over the past few years Test Automation has evolved as a big asset for software testing and it is not just appropriate for regression testing anymore. If we have a good test automation pack, it can help to improve lots of other things like team performance, sprint velocity, shorter release cycles, and provide confidence in releases.
It also gives testers the opportunity to spend more time on exploratory testing (where they can find more bugs) and teams can create quality products. Now we are in a position to automate most of the functional and non-functional aspects of applications with the different automation tools and technologies available.
Some examples are listed below but there are many more out there:
Web/Desktop Applications – Selenium Webdriver, Waiter, QTP, QAwizardpro, Eggplant, Applitools
Mobile Applications – Appium, Calabash, Eggplant, Applitools
Web Services/Api – SoapUI, Jmeter
Performance/Load – Jmeter, LoadUI, Visualload
DevOps – Puppet
Also as Devops is playing a major role in faster product developments now a days, if we can make use of best QA/Devops practices it can rapidly change the way we are delivering software to end users.
One of the major problems with today’s Test Automation is that if we don’t set up the framework properly at the start, we will spend time fixing broken tests, refactoring the framework and filling the gaps with manual testing.
And as QA and Devops teams are not working together in most cases we are failing to identify any issues related to products that are caused by in-fracture failures in early product development stages.
In this talk Mahesh will use his experiences to give an overview of:
Mahesh has 6 years of experience in software testing and currently works as QA Engineering Lead in Reed Business information.