{"id":21032,"date":"2023-02-25T04:00:41","date_gmt":"2023-02-25T04:00:41","guid":{"rendered":"https:\/\/www.softwaretestinghelp.com\/?p=21032"},"modified":"2025-05-09T10:57:16","modified_gmt":"2025-05-09T10:57:16","slug":"ranorex-tutorial-2","status":"publish","type":"post","link":"https:\/\/www.softwaretestinghelp.com\/ranorex-tutorial-2\/","title":{"rendered":"Ranorex Test Suite & Test Module, UserCode File and Xpath"},"content":{"rendered":"

In this tutorial, we will get to know about Ranorex test suite & test module creation, the UserCode file, Editing the Xpath, Data Binding, and Ranorex Report in detail.<\/strong><\/em><\/p>\n

In the previous Ranorex part 1 tutorial<\/strong><\/a>, we discussed the basic components of Ranorex Studio. Ranorex Studios offers a wide range of tools to make automation testing easier.<\/em><\/p>\n

However, Ranorex is considered to be an important automation testing tool having some excellent features in it. Ranorex is very simple and easy to use. Let’s dive deep into other factors involved in Ranorex through this article.<\/p>\n

Ranorex<\/h2>\n

\"Ranorex<\/a><\/p>\n

Modify the UserCode file<\/h3>\n

As discussed earlier, the recording file is made up of two files: .cs and.UserCode.cs file<\/strong>. .cs file cannot be modified. Any changes to the steps or further validation can only be added to the.UserCode file. .cs file is system generated and is used during compilation. User code is used for custom code entry.<\/p>\n

Let us create a test and modify the actions using.UserCode file. Follow the general steps to create a Ranorex project and record a test using the recording module.<\/p>\n

Refer to the image below:<\/strong><\/span><\/p>\n

\"Creating<\/a><\/p>\n

A Project by the name UserCodeProject.rxtst has been created. There is a recording module renamed UserRecord…rxrec. I have recorded a simple test of opening the MyComputer window from Start and closing the window.<\/p>\n

Open the .cs file for the recording module.<\/p>\n

It will look like something as shown below:<\/strong><\/span><\/p>\n

\"Recording\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/a><\/p>\n

ITestModule is a base interface that is implemented using a Run method.\u00a0 The Run method calls will contain all the recorded steps.<\/p>\n

Please consider the above E.g.<\/strong><\/em><\/span>, it has Clicked on Start Button, Click on Computer followed by Closing. This file gets compiled and executed during each Run, and it is generated automatically based on the recorded steps and modified user code. Hence no changes can be made to this.<\/p>\n

Now let’s see how we can add or edit the UserCode file. The UserCode file without any entry will only have the Init method.<\/strong><\/p>\n

\"UserCode<\/a><\/p>\n

I am going to add a new method to the UserCode file, OpenControlPanel()<\/strong><\/p>\n

\"Adding<\/a><\/p>\n

Go back to the Recording file (.rxrec) where all the steps will be in tabular form. Now try to add this newly created method.<\/p>\n

\"Adding<\/a><\/p>\n

\"Open<\/a><\/p>\n

Click on Confirm Selection. The method gets saved as a step in the recording file.<\/strong><\/p>\n

\"Confirm<\/a><\/p>\n

Now let us check what has happened to .cs file.<\/span><\/strong><\/p>\n

\"Check<\/a><\/p>\n

As and when the application becomes complex, the conditions to be tested also grow. And so, grows
\ntest scripts. Hence, it is very much necessary to have them divided into smaller identifiable modules. The OpenControlPanel() has been automatically added to the. cs file after saving the recorder file. Hence, you can jump directly to the generated code for any recorded steps by simply clicking on the step and clicking on the View Code option.<\/p>\n

Test Cases and Test Modules<\/h3>\n

We came to know how to create and modify test steps from the above example. We will now look at the ease of dividing these test steps into modules for better maintenance. As and when the test size increases, the number of steps also increases. Furthermore, it will become too difficult to maintain.<\/p>\n

Let us create a test suite and a recording module in it.<\/strong><\/p>\n

\"Create<\/a><\/p>\n

Here, Recording1 is the first recording module for TestCase1. Now let\u2019s see how to create multiple recording modules<\/strong> for TestCase1.<\/p>\n

\"Add<\/a><\/p>\n

Click on TestCase1 and select the Add option<\/strong>. Under Add, you have a drop-down as a New recording Module<\/strong>. Click on that and give a name to the recording module.<\/p>\n

I have created three recording modules for TestCase1 as shown below.<\/span><\/strong><\/p>\n

\"Creating<\/a><\/p>\n

Each recording module can have its own test steps inside them. It is also possible to Move, Cut, Copy and Paste the test steps from one recording module to another.<\/p>\n

Data Binding<\/h3>\n

This is one of my favorite topics in Ranorex. Often our tests will be based on different sets of inputs. We test our application for a state with different input conditions and then verify the output. This is called Data-Driven Testing and Ranorex offers a feature called Data Binding<\/strong> to bind the different Input conditions to the test case.<\/p>\n

To bind the data, click on the Test case => Select Data Binding<\/strong><\/span><\/p>\n

\"Data<\/a><\/p>\n

Ranorex offers data binding in 4 ways, as shown in the image below:<\/span><\/strong><\/p>\n