Running TestComplete Tests

Prerequisites

Configure the Build Plan to Run TestComplete Tests

Run the Build Plan

1. Open an interactive user session on your agents.

   To open the user session manually, you can log in to the agent by using Windows Remote Desktop.

   As an alternative, you can use third-party tools to open the user session.

2. If needed, create capabilities and requirements to specify agents on which your job will run TestComplete tests. See Specifying Agents to Run TestComplete Tests.

3. Place TestComplete test files to a location where TestComplete (or TestExecute) on your Bamboo agent can access them.

   If you store your TestComplete in a source control, configure your build plan to get the TestComplete project files to a needed location:

   

   Click the image to enlarge it.

   Note:

   We recommend that you add your TestComplete project files to source control directly from TestComplete IDE. This way, only the necessary files will be added. See Integration With Source Control Systems.

   As an alternative, you can place your TestComplete test projects to a shared network folder.

4. If you run TestComplete tests by using a script file, place that file to a location where the appropriate utility on your agent can access it.

You can use the Script task to command your build plan to run TestComplete tests by using the TestComplete (TestExecute) command line.

1. In Bamboo, click Build > All build plans.

2. Select your build plan and click Configure plan.

3. Switch to the Stages tabbed page of your plan and click a job that you want to run your TestComplete tests.

4. Click Add Task and select the Script task in the Task types dialog:

   

   Click the image to enlarge it.

5. In the Interpreter drop-down list, select the tool you want to use to run TestComplete.

6. In the Script location drop-down list, select whether you want to run the inline script or a script file.

7. To run the inline script, enter the needed script commands to the Script body field.

   To run a script file, enter the path to the needed file.

   Configure your script to run TestComplete tests by using TestComplete command line.

   Specify the path to the TestComplete executable and the path to the TestComplete project or project suite you want to run. Use the /run command-line argument to command TestComplete to run tests.

   You can use various TestComplete command-line argument to specify tests you want to run, for example, the /p:project_name argument will command TestComplete to run all test items of the specified project. In addition, you can use command line arguments to configure TestComplete behavior during the test run, for example, the /SilentMode argument will command TestComplete to run in the silent mode suppressing all TestComplete dialogs and messages.

   For example –

   cmd.exe

   TestComplete.exe "C:\Tests\TestProject1\TestProject1.mds" /run /p:TestProject1 /SilentMode /exit

   

   Click the image to enlarge it.

   PowerShell

   $testcomplete = TestComplete.exe
   $project = 'C:\Tests\TestProject1\TestProject1.mds'
   $arguments = $project, '/run', '/p:TestProject1', '/u:Unit1', '/rt:Test1', '/ns', '/SilentMode', '/exit'
   Start-Process -FilePath $testcomplete -ArgumentList $arguments

   

   Click the image to enlarge it.

   For detailed information on the TestComplete command line, see –

   TestComplete Command Line

8. If needed, specify additional parameters of the Script task.

9. Save the changes.

In Bamboo, run your build plan:

Click the image to enlarge it.

The plan will run the task on your agents and command TestComplete to run the specified tests.

To learn how to configure Bamboo build plans to get TestComplete test results, see Getting TestComplete Test Results.

TestComplete 32-bit executable is located in the <TestComplete>\Bin folder.

TestComplete 64-bit executable is located in the <TestComplete>\x64\Bin folder.

TestComplete 32-bit executable is located in the <TestComplete>\Bin folder.

TestComplete 64-bit executable is located in the <TestComplete>\x64\Bin folder.