Regression testing software can help you make the manual regression testing process automated. It can save a lot of time and effort. But what is regression testing software? What should you look for when you are deciding on the regression testing tool of your choice?...
Leverage the data
Once you have your log files, it’s time to evaluate the information they contain. This will show you where you can gain the most benefits from improving your test. In this chapter, we’ll show you a few examples of evaluations that focus on typical reasons for unnecessarily long execution times.
Of course we can’t cover all scenarios, but these short examples can give you an idea on how to approach the wealth of information contained in the log files.
A time-by-event evaluation is a good way of finding out which event types take the most time.
Delay actions also take up 12 %. It’s a good idea to check out where you can replace those with Wait for actions, which only stop the test for as long as necessary instead of for a fixed amount of time.
Using the repository log, you can evaluate which repository items take the longest to be found and identified. This tells you which items you should take a closer look at, e.g. for adjusting the RanoreXPath to be quicker.
The time it takes individual test containers or modules to execute is also a useful metric. Use it to find out where your test suite is slowest, so you can make structural improvements, for example, or remove clutter from test cases and modules.