ArtOfTest.Runner

The ArtOfTest.Runner.exe is installed in your Test Studio installation directory. The default location is:

• C:\Program Files (x86)\Telerik\Test Studio\Bin

 

When working with the execution engine in the command prompt, make sure you always are running as Administrator and have the root directory in context as shown below so that you can call the runner directly.

 

 

Add Path to Environment Variables

It can get tedious to always have to navigate to the Bin directory each time you want to call the execution engine. A great workaround is to register this path with Windows so that you can call ArtOfTest.Runner.exe from any directory within the command prompt.

1. To do this, right mouse click on Computer and select Properties.

 



 

2. After the System screen appears, select Advanced system settings.

 



 

3. This will open the System Properties window. Select the Advanced tab and then the Environment Variables button.

 



 

4. Under the System variables section, scroll down and highlight the Path variable. Click the Edit button.

 



 

5. In the Edit screen, append the path to the Bin directory to the end of the string that already exists in the Variable value text box (with a semicolon before the path). In this example, I added ";C:\Program Files (x86)\Telerik\Test Studio\Bin - Notice that I added a semicolon to separate the previous path from the path to the ArtOfTest.Runner.exe directory.

 




 

6. Click the OK button. You now have access to the execution engine from any directory on your computer. Make sure you start a new instance of the command prompt to get the updated variables.

 

Options

Here is the Help Screen for ArtOfTest.Runner.exe:

 

Execution Options

There are the test=[file path] and list=[file path] execution options. Both of these options take file paths as the arguments.

 

The test option takes the full path to an individual test file with the .tstest file extension. This file will be located in your main project directory and under any folder structure you have created to organize your tests. For example:

 

ArtOfTest.Runner Test Execution syntax

ArtOfTest.Runner Test Execution result

 

There are a couple of things to note when using file paths in the command prompt:  

1. Ensure to double quote the path because of spaces in the file path.
2. Second, to prevent typing mistakes, use the clipboard paste option within the command prompt window. To find the paste option after copying the path to the clipboard, right mouse click on the top left corner of the command prompt and choose Edit > Paste.

 

 

The second execution option is the list=[file path]. This option provides for the execution of a test list which has many tests inside it. For more information about test lists, see:

• Test Lists
• Test List Settings
• The Power of the Dynamic Test List

 

Similar to the previous option, just include the file path to the test list which is a file with an .aiilist extension. All test lists for your project can be found in the test list folder under your project root folder.  For example:

 

ArtOfTest.Runner Test List Execution syntax

ArtOfTest.Runner Test List Execution result

 

Both of these options can be used by themselves for execution. After putting either option in the command line arguments, simply press Enter and either your test or test list will execute using all the default locations for outputting the results. By default, results will be stored in the Results folder under the project’s root directory.

Exit Codes

ArtOfTest.Runner returns an exit code so the Build Server can check for it on process exit in case of an exception:

 

Code	Title	Summary
0	RUN_TESTS_SUCCESS	Run is processed and all tests passed.
1	RUN_TESTS_ERROR	Run is processed and some tests failed.
2	NOT_RUN_UNEXPECTED_ERROR	Run is not processed due to unexpected error.
3	NOT_RUN_COMPILATION_ERROR	Run is not processed due to compilation errors.
10	NOT_RUN_USAGE_INFO	No run to process, requested usage info.
11	NOT_RUN_INVALID_COMMAND_ARGS	No run to process due to general invalid arguments error.
12	NOT_RUN_TEST_NOT_FOUND	Run is not processed due to invalid test path argument.
13	NOT_RUN_TESTLIST_NOT_FOUND	Run is not processed due to invalid test list path argument.