Skip to content

Semi-Manual Testing

Purpose

This technique is useful when you want a predominantly manual test (executed by a tester) to include some steps that are automated by Rapise. These steps could be initial setup tasks (e.g., logging in, starting the application) or simply tasks that are well-suited to automation.

Usage

Create your manual test using either the recorder or the manual test editor. Alternatively, you can open a test already created in Spira.

Next, within Rapise, create a test scenario (function) for the automated steps. In this example, we will simply automate the launching of MS-Paint.

Create a function in the User.js file with the following code:

function LaunchMsPaint()
{
    Global.DoLaunch('C:\\Windows\\system32\\mspaint.exe');
}

Now, navigate to the Manual Steps section of Rapise by clicking the Tools > Manual Steps menu.

For example, in the first test step, change the Description to the following:

@LaunchMsPaint();
//User starts up the MS-Paint Application

This will be displayed within the test step itself:

semi_manual_1

Now, when you execute the test (using the normal Execute button on the main Test toolbarnot the Execute Manual icon on the Manual Toolbar), Rapise will execute the main Test() function, which contains:

function Test(params)
{
    Global.DoPlayManual('ManualSteps.rmt');
}

g_load_libraries = ["UIAutomation"];

This instructs Rapise to use the manual playback system. However, when it reaches the first step, Rapise will recognize the at symbol (@), which indicates an automated scenario, and then call the following code:

//User starts up the MS-Paint Application
LaunchMsPaint();

Once the scenario has completed, Rapise will return to the manual test playback.

See Also