Model-Based Test Automation for Ranorex

Rigorously Test Fast-Changing Applications

Generate optimised scripts and data from Ranorex repositories, rigorously testing fast-changing applications. Test Modeller and Ranorex remove the need for slow and complex scripting, creating bespoke automation from quick-to-build flowcharts.

‘Manual’ Test Automation is too Slow for Short Iterations

Automated test execution is a requirement for testing today’s applications in short iterations. However, organizations today are struggling to achieve sufficient rates of automated testing, as automation introduces new bottlenecks. Most frameworks require slow and complex scripting, but QA teams lack the time and engineering skills to write thousands of scripts each sprint. The tests burn through data at phenomenal speed, but test data provisioning cannot keep up and invalid combinations lead to test failures. Each time the system changes, engineers must furthermore check and update scripts and data manually, and quickly there is a bigger backlog than there are hours in a sprint.

From Application Scans to Test Execution in Minutes

With the integration between Ranorex and Tess Modeller Modeller, testers with and without coding skills can become the fastest automation engineers. Easy-to-use recorders and the Ranorex Spy build object repositories automatically from scanned UIs, creating executable code without slow and complex scripting. The scanned modules can be pushed automatically to Test Modeller, ready to generate optimised tests and data from quick-to-build models.

ranorex testing

Building models in Test Modeller is as quick and simple as selecting from the imported models. “Fast Modelling” automatically identifies the equivalence glasses associated with each selected element, quickly creating complete flowcharts to drive rigorous testing. Automated data definition assigns synthetic test data generation functions to each element, before applying test generation algorithms to compile optimised tests and data. This creates the smallest set of Ranorex tests needed to “cover” all the logic in the modelled application, detecting defects earlier, and at less cost to fix. Testers in future iterations then only need to update the central flowcharts, rapidly regenerating Ranorex tests and data.