Software testing has become a more and more significant step in the process of developing. As requirements and expectations grow in IT organizations, the relevance of testing grows in the case of small and big companies as well. The process has two main parts: manual and automation testing and they have the same types, but the essential difference between them is the way of execution. Both types of testing have pros and cons, so testers have to choose the good one in the given situation. In this text the issue of automation testing will be discussed, more precisely the problem of how could a developer who has not done this kind of projects before start it and which is the best way to go.
Test automation offers a possibility to improve the efficiency of the testing. Once automated tests have been developed, they can be run quickly and repeatedly. It could be a cost-effective method for the testing of software products.
There are two general approaches to test automation:
- Code-driven testing: The classes, modules and libraries are tested with a variety of input arguments to validate that the results that are returned are correct.
- GUI testing: A framework creates user interface events for instance keystrokes and mouse clicks, meanwhile recognizes the changes that result in the UI, to validate that the observable behavior of the program is correct.
The first step is to find the scope of testing. First the tester has to choose the fields of the software that has to be examined. Besides that it has to be decided what kind of result is that which counts as successful and what means failure. Without doing the above mentioned things the tester could not tell whether the software had passed the test or not.
Generally these products are made for payment and the amount of money paid to the teams gives a limit to the possibilities. Because of that some tasks are more important to be done. The client has to understand that their investment into the process will not result in immediate benefits, but they can save money with its help because the number of occurring problems could be reduced to a minimal. These automation tests could be used more than once so they save money and time as well. Therefore the best tool has to be chosen to finish with process cost-effectively. Developers cannot make the testing totally automatically, because it is not possible.
Before creating the framework the developer has to know what is to be done. It is very important to the person who does the testing to get to know the basics of automation testing. The process of development resembles to the process of software development so knowing this could help the tester. The main idea is that the worker has to create scripts for every kind of processes like communication with the systems, with the data base, peripheries and besides that logging and error handling. Two types of scripts could be made: driver script and worker script.
Driver script: Scripts that execute a set of transactions by invoking relevant re-usable components for each test case.
Worker scripts: They are group of driver scripts to execute in a batch mode.
To reach re-usability Record/Replay, Transaction to identify different scenarios to execute scripts in batches, Action/Keyword, Data Driven method can be used.
The benefits that are given by automation testing can help the developer to increase the quality of the product so it can be used safely on market.
Similar Posts from the author:
- Getting started with Android automation testing
- Page Object pattern and Page Factory
- Event logging with aspects in automated testing
- Getting started with Webdriver python guide
- Graphwalker – how to start guide
One thought to “Overview of automated testing”
nice
it really helpful for me
thanks
Comments are closed.