Speed-up Test Automation with Vortex
A good automation framework should have clear standards and, at the same time, should be generic and flexible enough to be applied to different realities or processes. E-Core’s Vortex is a framework built on top of HP QuickTest Pro (QTP), designed to provide more efficiency to Automation teams.
Vortex follows 3 basic principles:
- Organization: focused on clear standards, central repositories, usage of parameterization and correct integration with HP Quality Center;
- Abstraction Layer: a function-based part of the framework which is responsible for simplifying the script coding and which integrates the reporting system on its core;
- Effective Reporting: works based on the QTP’s reporting method, but expands it to show results in a clear and structured format
Currently, e-Core is implementing Vortex in one of its customers located in Tampa Bay, Florida. Being a digital marketing company, the customer relies on IT to support its core operations.
The implementation of Vortex presents advantages over conventional approaches used before for automation with QTP (Record/Playback), such as:
Standardization: When everybody uses the same standards, it is easier to understand what is being done and the entire team has an organized way to work, speaking the same language. If more projects adopt the same standards, the integration along the testing area at the company increases as well, especially for different projects;
Lower Maintenance and Cost: Organization, by itself, makes things simpler, but the abstraction layer can also reduce code size and improve code legibility. Also, a Central object repository approach makes maintenance easier, once there is no need to change all scripts when an object changes.
Increased Productivity: Once codes are smaller, test engineers are able to design more scripts in the same time they would design one single script using the conventional approach. It also allows them to report and show testing results faster.
After implementing Vortex in our customer, it was possible to establish some comparisons between what was being done previously to what is being done today.
- Automation engineers had 2 works: Recording and organizing the code (commenting, indenting, etc.);
- Script development was totally dependent on the tool’s coding standards;
- Scripts were larger and less clean, because of the QTP syntax, comments, etc.
- Automation engineers can code directly, without the need to record all actions (code is automatically organized). Maintenance and readibility become easier because the code is clean. Therefore script development is faster as well;
- Manual testers can also run automation, once they do not need to have QTP on their machines. They can do that via Quality Center;
- More time spent on the functions, not on coding the scripts. Once functions are coded only once, time is for the scripts. At the same time, scripts get smaller, syntax is simpler, there are much less LOC and comments (decreases development time, increases productivity);
- Results are reported in a clearer way and can be shared by e-mail, because there is an option to generate them in simple .html files.
Vortex is a powerful tool that can be used to improve quality, reduce costs and increase productivity, helping software teams to produce better software.