Running tests from command line

To run tests from a command line you need to use the command line option /b. When RIATest is invoked with this parameter it works in 'batch' mode. In batch mode no GUI is opened, RIATest is only capable of running tests. To specify the project to run you need to use option /p. You will also need to tell RIATest to run the project using option /r. So the minimum command line to run a project in batch mode is the following:

riatest.exe /b /r /p c:\mypojectdir\myproject.rtp

It will execute and return exit code 0 on success or other exit codes on failure. You can also use the environment variable RIATEST3:

"%RIATEST3%\riatest.exe" /b /r /p c:\mypojectdir\myproject.rtp

The RIATEST3 variable points to the installation directory not to riatest.exe. This is done on purpose so that you can also refer to other files such as "%RIATEST3%\agent\RIATestAgent3.swc" in the build tool.

To run RIATest in batch mode on the Mac OS X use the following command:

"/Applications/RIATest 3/RIATest.app/Contents/MacOS/RIATest" -b -r -p Components.rtp

You can also add RIATest to the PATH to make the command line shorter. Add the following to your .bash_profile file in your home directory:

export PATH=$PATH:/Applications/RIATest 3/RIATest.app/Contents/MacOS/

You can now use a shorter command to execute RIATest:

RIATest -b -r -p Components.rtp

Calling RIATest from Apache Ant

You can use Ant's built-in exec task to call RIATest from your ant projects. For example:

<target name="test" description="test the project">
  <property environment="env"/>
    <exec dir="." executable="${env.RIATEST3}\riatest.exe" failonerror="true">
      <arg line="/b /r /p Components.rtp"/>
    </exec>
</target>

If the failonerror attribute is set to true, the entire Ant build will fail if RIATest test fails (riatest.exe returns non-zero value).

Running individual scripts or groups

Normally the batch mode will run the entire project specified by option /p. However sometimes you may want to run only a few scripts or groups from the project. This can be specified in two ways: by supplying scripts to execute on a command line (option /rs) or by supplying a file that will list the scripts to run (option /rf).

Important: options /rs and /rf are effective only when used in combination with option /b.

Specifying scripts to run from command line (option /rs)

Option /rs allows you to specify individual scripts or groups to run. The /rs option should have a list of scripts/group to enable (using + sign) or disable (using - sign) from running. The separator symbol for the list is a semicolon.

For example we have two groups: GroupA and GroupB, GroupA contains scripts Script1.rts and Script2.rts and GroupB contains Script3.rts and otherdir/Script4.rts. Note that Script4.rts is located in otherdir sub-directory.

To run only Script3.rts use command line /rs -//GroupA;-//GroupB;+//GroupB//Script3.rts or simply /rs -//;+//GroupB//Script3.rts

To run Script1.rts from GroupA and Script3.rts from GroupB use command line /rs -//;+//GroupA//Script1.rts;+//GroupB//Script3.rts

To run only Script4.rts use command line /rs -//;+//GroupB//otherdir/Script3.rts
Note the use of single slash to separate script file's directory and file name.

The rules for /rs option specifier are:

• Start any path with a double slash //
• Delimit groups with a double slash //
• Place double slash // after the last group name if it will be followed by script name.
• Use single slash / as path separator in script name if neccessary.
• Use -//; to disable entire project.
• Surround the entire option with double quotes " if there is a space, semicolon or other special character in the group or script name
• The order of terms delimited by semicolons is important. Terms on the right override terms on the left, i.e. you can disable an entire group, then continue and enable one or several scripts in that group.

Specifying scripts to run in a file (option /rf)

The /rf option allows you to list the scripts to run in an external file. The external file must be in INI format. RIATest will read section [ProjectView/DisabledScripts] and will NOT run scripts found in this section. The format of the file is the same as the .rtw file generated by RIATest IDE so you can run RIATest, open your project, enabled/disable scripts/group the way you want, exit RIATest and the .rtw file will contain [ProjectView/DisabledScripts] that you can copy to your own file and pass it using /rf option.

Outputting results to HTML file

When running in batch mode RIATest can output the results of the test execution to plain text (option /o) or XML files (option /ox). If you want the results to be in HTML format you need to use the separate rtxml2html converter utility. First, tell RIATest to run the tests and output results to XML file:

riatest.exe /b /r /p c:/myproj.rtp /ox results.xml

Once the tests are finished use rtxml2html to convert the results to an HTML file:

rtxml2html /i results.xml /o results.html

Passing data from command line to scripts

If you need to pass data to your scripts when running the scripts from the command line you need to use option /d and the script function getProjectGlobal().

From the command line pass data this way:

riatest.exe /b /r /p c:/myproj.rtp /d "name1=val1;name2=val2"

Note that multiple values are supported and should be delimited by a semicolon.

In your scripts read the values are passed from the command line in this way:

var val = getProjectGlobal("name1");

Command line parameters reference

Exit codes

When executed in batch mode riatest.exe returns the following exit codes: