Why do we need automated testing?
Automation is one of the best ways to test how well your current software is performing versus previous versions. In other words, automation is about detecting regressions and running different inputs. Until it becomes possible to write automated scripts for your application, many errors that can be detected during the script writing process will already be successfully found and eliminated.
Many automation bugs are discovered during the actual writing of automated scripts. During the actual implementation of automation, only a few new software errors can be detected, although errors can be found when performing automation in different configurations or across datasets.
However, automation is associated with management because it saves time, hardware, resources, and software testers that a software testing company uses to deliver a high-quality product. For many automation projects, it is difficult to determine what is expected of them, because those who perform automation do not understand that automation is just another tool that can be used to test software.
Automated testing is used to a greater or lesser extent in almost every project. It does not make any guarantees or protect the product from poor performance, while software testing will improve the quality of the product. Poorly implemented automation will ultimately cost more time and effort than no automation. However, if implemented, it will bring significant benefits. You need to understand that automation is only needed to evaluate regressions and be a “monkey tester”, which does not mean running the same test every day in the same way. Ignoring this task, software testers can follow simple steps and use their creativity and intelligence to find new bugs.
Only 5-20% of all software bugs are found during automated regression testing. Considering the fact that automating test cases can be 10 times more expensive than manually executing them, without considering the support and maintenance of the test code, test cases for automation should be chosen very carefully.
The translation of the material was prepared as part of the course “Java QA Engineer. Basic”.
To become a good automator, you need to know not only programming languages and frameworks for automation, but also testing theory. On a two-day online intensive we will learn what testing is and where it came from, who a tester is and what he does. We will study software development models, testing life cycle, checklists and test cases, as well as defects. In the second lesson, we will get acquainted with one of the main task and defect trackers – Jira, and also practice in TestIT – a domestic development for solving problems of testing and ensuring software quality. Join us!
