Track by recording
Track by recording is the regular way of tracking UI-elements during the recording of a test case. Although this default tracking method has been used during numerous fundamental chapters it is explained for the sake of completeness herein.
In this chapter
Test example definition
To explain the concept of tracking a UI-element by recording, a simple test example is defined. All necessary test functionality is implemented within the database working environment of the demo application.
Track by recording – test example definition
Test database working environment for test example
Track by recording
Now let’s see how track by recording actually works.
Start the demo application and select the test database working environment
Start Ranorex Studio and open a new test solution with a meaningful name
Start instant recording of demo application
Choose Instant recording to record the already started demo application
Track a radio button in the demo application
Click STOP in the recorder control center and end recording
Track by recording result(s)
When recording is ended, Ranorex Studio opens up the working environment and displays the recorder view with action list and current repository.
Track by recording – action list
Track by recording – repository
The repository contains the tracked & identified
RdbFemale Along with the name, a unique identifier (the so-called RanoreXPath) is stored. This identifier specifies the position of the corresponding UI-element within the GUI and helps to uniquely identify and describe the UI-element
- During recording mouse clicks, user inputs, mouse movements (if activated) and other user interactions are tracked
- Ranorex identifies the corresponding UI-elements and stores them with an inner representation as repository items
- Usually, every UI-element is only referenced by one repository item in the repository
- Ranorex recognizes if a UI-element is involved more than once and then re-uses already identified repository item(s)