Image-based automation

Automated software testing usually is based upon the recognition of user-interface elements (UI-elements). Many of them may be identified based on text. Alternatively, the recognition of pixel images instead of text is necessary for test automation. Here – image-based automation is a well-proven method to identify, detect and apply UI-elements. Everything needed to make use of this method is introduced and explained herein.

In this chapter

Sample solution

The herein introduced concepts are put into a sample solution which can be downloaded. You are invited to experiment with the sample solution and improve your knowledge.

Installation:

Unzip the project directory to any folder on your computer
Start Ranorex Studio and open the solution file ImagebasedAutomation.rxsln

Turning image-based automation on/off

Image-based automation is turned on and off in the Recorder control center any time during recording.

Image-based switch in Ranorex Recorder (turned off)
Image-based automation turned on

Press I to activate image-based recording.

Why image-based automation?

The reasons for using image-based automation within automated testing of GUI software might not be obvious. This section is to show you at least one reason where text-based automation fails, and image-based automation is the solution.

Example preparation

We’ll use the Ranorex Studio Demo Application for our example. To record our actions, we’ll use the instant recording functionality of the Ranorex Recorder.

In the recording module view of Recording1, click RECORD.

Text-based recording

Track & record three (3) consecutive dates in the calendar view of the demo application in the default text-based automation mode and see the result.

Test recording result

See the result of the successful test recording when the test run is started:

• The recorded calendar dates are identified correctly
• Each click action in the report corresponds to the correct date in the calendar

Change of test conditions

Assume that the test conditions change – and – that the calendar view changes to a different month due to time progress between recording and replaying the test.

Watch the result of the test run with the previous recorded calendar dates:

Result interpretation

• The test runs without failure and reports a success (see test report)
• But – the result is wrong, as dates at the originally tracked positions in the calendar are identified during the test run, and not, the correct dates at their changed position!

Conclusion

In the next chapter, we show you how image-based automation overcomes this challenge.