Analyzing recordings | Ranorex
HomeUser GuideRanorex Studio FundamentalsAnalyzing recordings

Analyzing recordings

Within this section we introduce the Recorder working environment and analyze the recording of the current test example.

In this chapter

    Recorder working environment

    The Recorder working environment basically identifies four different regions which are explained herein after.

    Project file view
    The upper-left screen area identifies the project file view of Ranorex Studio. There, all files being created and managed for a test project are displayed in a folder-like structure.

    Project file view

    Module browser view
    The lower-left screen area hosts the module browser view. This storage structure plays a central role in modularization of test recordings and with test modules.

    Module browser view

    Further reading

    The module browser view and its application is introduced and explained in > Ranorex Studio fundamentals > Test suite > ⇢ Introduction

    Action table

    • The recording steps lead to a list of recorded actions
    • These actions are listed in the sequence of their appearance in the action table
    • The current example identifies 7 actions
    Recorder action table

    Further reading

    The fundamental concept  of action is introduced and explained in > Ranorex Studio fundamentals > Actions > ⇢ Introduction

    Repository

    • During the recording, all identified UI-elements (i.e. buttons, text fields, links, menu items, …) are being tracked and referenced through repository items within the repository
    • Each UI-element is referenced by one repository item
    • The current example identifies 5 UI-elements
    Repository with referenced UI-elements

    Further reading

    Repositories and their use and appliction are introduced and explained in > Ranorex Studio fundamentals > Repository > ⇢ Introduction

    Action table analysis

    The action table identifies 7 different actions. Let’s have a closer look at those actions.

    Example action table

    Example action table

    Run application action

    • The action starts the application under test at the beginning of the recording

    Mouse click action

    • This action represents the click into the name text field to place the input-cursor in the field
    • The last column of this action contains a reference to the corresponding repository item which represents the UI-element ‘EnterYourName’ (i.e. the name text field)

    Key sequence action

    • This action represents the text input into the name text field
    • The current example outlines the input of ‘Harry’ as text into the UI-element ‘EnterYourName’ text field

    Mouse click action

    • Action #4 refers to the click on the Submit button in the test application
    • The reference to the UI-element, i.e. the ‘Submit’ button can be seen in the last column

    Validation action

    • The test validation is represented as an action item
    • Ranorex matches the text in the changed welcome message against a reference text

    Mouse click action

    • The click action represents the resetting of the welcome message to its initial content

    Mouse click action

    • The final action represents the click on the Exit button of the application under test
    • This action closes the application

    Further reading

    The fundamental concept of action is introduced and explained in > Ranorex Studio fundamentals > Actions > ⇢ Introduction

    Repository analysis

    The current example identifies 5 repository items which each refer to a corresponding UI-element in the application under test. Let’s have a closer look at them.

    Example repository

    Example repository

    Item #1 – RxButtonExit

    • This UI-element represents the Exit button of the demo application

    Item #2 – EnterYourName

    • This UI-element represents the name text field of the demo application

    Item #3 – BtnSubmitUserName

    • This UI-element represents the Submit button of the demo application

    Item #4 – Reset

    • This UI-element represents Reset link (i.e. button) of the demo application

     Item #5 – LblWelcomeMessage

    • This UI-element represents the text label which contains the welcome message of the test application

    Further reading

    The fundamental concept of a repository is introduced and explained in > Ranorex Studio fundamentals > Repository > ⇢ Introduction

    Link between actions & repository items

    Recorded actions and repository items referencing identified UI-elements are managed and stored separately, but they are linked to each other. This concept is briefly explained herein.

    Link between action and repository item

    Link between action and repository item

    Actions referencing UI-element(s)

    • The mouse clicks on the name text field (action #2), as well as the text insertion of ‘Harry’ into the name text field (action #3), refer both to the same UI-element ‘EnterYourName’ (item #2).

     

    Repository item referencing a UI-element

    • UI-elements are represented by so-called repository elements
    • They have a name (e.g. EnterYourName) and a location in the GUI (=path)

     

    Further reading

    The link between actions & repository elements is introduced and explained either in > Ranorex Studio fundamentals > Actions > ⇢ Actions & repository items, or in > Ranorex Studio fundamentals > Repository > ⇢ Repository items & actions.

    Sample solution

     

    We offer to download a prepared sample solution for this chapter.

    Training! What do I do?

    Theme: Analyzing recordings
    Time: Less than 10min

    Download sample file

    Installation:

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