Rapise 8.0: how to use Page Objects/Modules

When writing automated tests, it is often necessary to create shared modules that can be used by multiple test cases. These modules serve various purposes, such as handling authentication for applications with a login page, performing necessary actions after test case completion, or working with custom controls within the application, such as dropdown menus, form fields, or grid/table controls.

In Rapise 8.0, you have the ability to address all these requirements. Rapise supports two types of modules: RVL (Rapise Visual Language) and JavaScript-based modules. These modules provide a flexible and powerful approach to handle common functionalities across your test cases.

By using RVL modules, you can visually create reusable components that encapsulate specific actions or sequences of steps. For example, you can create an RVL module that handles the authentication process by entering credentials and clicking the login button. This module can then be easily reused across multiple test cases that require login functionality.

Alternatively, you can leverage JavaScript-based modules in Rapise 8.0. JavaScript is a versatile programming language that allows you to create custom functions and logic to handle complex scenarios. With JavaScript-based modules, you can implement specific interactions with custom controls or perform actions that are not easily achievable through the visual interface of Rapise.

Both RVL and JavaScript-based modules in Rapise provide a seamless way to organize and reuse common functionalities within your automated tests. They help improve maintainability, reduce duplication of code, and enhance overall test efficiency.

RVL-based Module

Let's take a look how it works. First we will create a new Test Automation Framework.

Name it PageObjectsDemo and choose Web test type.

Choose Chrome browser profile.

In the Object Tree pane right click Modules/Pages and choose Create Module/Page Object.

Give it a name LoginPage and click Create button.

We are going to create an RVL module, so choose RVL option.

LoginPage RVL will be created.

And LoginPage module will appear in the Object Tree.

Our page object has a default action DoAction, you may see it's name in RVL tabs. Double click it and change to DoLogin.

Define two input parameters for this action: USR, PWD.

We will now record a login sequence of steps on https://libraryinformationsystem.org with credentials librarian/librarian. Make sure that the LoginPage RVL document is still active and click Record button on the toolbar. You will see the Choose Test Case dialog with LoginPage selected.

Click OK and record the login scenario. Enter the URL when prompted.

Click the Log In link.

Enter username and password and click Log In button.

Click Finish in the Recording Activity dialog.

Select line 10 and click Insert Here button.

You will see the steps inserted.

Bind Username and Password fields to USR and PWD input parameters.

DoLogin action is ready to use. Let's now create one more sheet DoLogout.

Click Record on the toolbar, click OK in the Choose Test Case dialog. Rapise will reconnect to Chrome. Just click on Log Out link.

Click Finish in the Recording Activity dialog.

Insert the recorded steps, remove the default parameter for the DoLogout action. You will see the result.

We are now ready to create the very first test case.

In CheckLogin RVL use LoginPage module like this:

You may now run CheckLogin test case, just click Play icon against the test case name.

After execution you will see the report:

If you wish to close the browser at the end of each test case please refer to Recommended way of executing code before and after each test case.

JavaScript-based Module

Let's now create JavaScript module with name GridModule.

GridModule.js will be created and opened.

Change it to


/**
 * @PageObject GridModule description
 */
SeSPageObject("GridModule");

/**
 * Get the number of rows in the main grid
 */
function GridModule_GetRowCount() /**number*/
{
	var /**HTMLObject*/ tableObj = Navigator.SeSFind("//table[@class='dataGrid']");
	if (tableObj)
	{
		var rowCount = tableObj.DoDOMQueryValue("count(.//tr)");
		return rowCount - 1;
	}
	return -1;
}

Now we may use it in a test case. Let's create new test case with name CheckGrid by cloning existing test case CheckLogin.