User guide content example | Ranorex
HomeUser guide content example

Recording a test

Use the Ranorex Settings to adjust the test automation software to the needs of your working environment, test execution, project and tetchnology.

Structure of this chapter

    H2 Headline should also be used as anchors for the sections

    Settings can be divided into two groups: user settings and solution settings. Each setting belongs to one of these groups.

    User settings are always stored locally on a machine and include user specific settings related to the Ranorex Studio working environment. Find out more about user settings

    Supercool. well done Mirza

    Solution settings include all settings which relate to the test solution, such as plugins, RanoreXPath generation, Ranorex Recorder defaults and many more, which can be shared between different systems, within teams and also be put under Version control.

    This is another headline for better structuring if needed

    Solution settings include all settings which relate to the test solution, such as plugins, RanoreXPath generation, Ranorex Recorder defaults and many more, which can be shared between different systems, within teams and also be put under Version control.

    Additional infos to solutions can be found under: ⇢ Test validation

    Where to access settings

    There are three ways to open the settings dialog:

     Click on the Settings button within Ranorex Studio.
     Click on the Settings button within Ranorex Spy.
    tipp icon

    Please note

    Do not change the name of the folder or the file. If you remove the settings file (“Ranorex.rxsettings”), the solution settings stored on the local machine are automatically used during test execution. If you open the settings file, it is shown in its raw format. It is not recommended to edit the file in this view.

    tipp icon

    Screencast

    The screencast “Quick Start with Ranorex Test Automation” gives a short introduction to the Ranorex Recorder. You can jump directly to the noted position in the video by clicking:

    http://youtu.be/0S_YC7uwI-s#t=1m8s.

    tipp icon

    Hint

    The screencast “Quick Start with Ranorex Test Automation” gives a short introduction to the Ranorex Recorder. You can jump directly to the noted position in the video by clicking:

    http://youtu.be/0S_YC7uwI-s#t=1m8s.

    tipp icon

    Attention

    Unless recording is active, and you do not pause, every user interaction on the screen is being recorded in the actual recording session.

    Recording a Test

    In the following section you will create a new Ranorex Test Solution and record the process for adding an entry to KeePass.

     Start Ranorex Studio and open the empty recording file.

    Open Ranorex Studio by choosing Start>Programs>Ranorex>Ranorex Studio. Click the New Test Solution… button to create a blank test suite project.

    Ranorex Studio Startpage

     Click the Create button and a new test suite project opens.

    New Ranorex Test Suite containing one test case using an empty recording

    To start up a project click on blablabla or use the shortcut + ESC Maybe we could find a solution to have more icons like this.

    Should be doable by just copy paste the character like here: ⇪⇧⇥ ↩← ↑ → ↓⌘⌥

    Set up a new project

    In the following section you will create a new Ranorex Project and lorem ipsum dolor sit…

    Easy workflows that are doable in one dialog or similar, should be described with animated gifs. Could be easily done with p.ex http://gifmaker.me/ – See example here: https://goo.gl/ZRjJnL

     In the New project dialog click on Advanced
    Select Console Application from Templates
    Type in a Project name and click on Create

    Structure of a test suite

    This sample includes different types of elements which can be used within a test suite and covers all possible combinations.

    Test suite: Represents the entire test suite and is the root level of the structure

    Mazim enim illum lectorum consequat dolor. Ut insitam qui option ipsum nulla. Ad fiant vero diam zzril ii. Mazim enim illum lectorum consequat dolor. Ut insitam qui option ipsum nulla. Ad fiant vero diam zzril ii. Mazim enim illum lectorum consequat dolor. Ut insitam qui option ipsum nulla. Ad fiant vero diam zzril ii.

    Test case: Represents a test case

    • This is fact one and its says blablabla
    • This is fact two and it says rororo
    • This is fact three and it says uiuiui
    Setup: Represents the setup

    Training! What do I do?

    Theme: Creation of test example
    Time: Less than 10min

    Download sample file

    Reference

    A complete list of actions with their type, function and possible application can be seen in:

    Ranorex Studio fundamentals > Ranorex Studio Overview > ⇢ Actions

    namespace KeePass { /// /// Description of AddCredentialEntry. /// [TestModule("03F5603B-0DDC-49AA-8C26-4D8088260C66", ModuleType.UserCode, 1)] public class AddCredentialEntry : ITestModule { /// /// Constructs a new instance. /// public AddCredentialEntry() { // Do not delete - a parameterless constructor is required! } /// /// Performs the playback of actions in this module. /// /// You should not call this method directly, instead pass the module /// instance to the method /// that will in turn invoke this method. void ITestModule.Run() { Mouse.DefaultMoveTime = 300; Keyboard.DefaultKeyPressTime = 100; Delay.SpeedFactor = 1.0; } } }