TestComplete Test Step

About TestComplete step

Use the TestComplete test step to run TestComplete tests as part of your ReadyAPI test cases.

Requirements

  • pro.png To use this test step, you need ReadyAPI Test Licenses. If you do not have it, you can request it on our website or start a trial.

  • This test step can run only on computers working under a Windows operating system.

  • To run the test step, you need to have either TestComplete or TestExecute on your computer.

    Tip

    You do not need TestComplete or TestExecute to create and configure the test step. That is, you can do this on Linux or Mac computers.

  • On Windows 8 and later, you must run ReadyAPI and TestComplete with elevated permissions if you want to use the TestComplete test step.

  • To run the test step on Windows 10, you need to disable the Enable support for testing Windows Store applications option in your TestComplete.

  • You need to copy your TestComplete project to the computer, where you are going to run your ReadyAPI test.

Important

The test step fails to start if TestComplete or TestExecute is already running in the system. You need to close running instances of these products before the run.

Editing TestComplete test step

You can modify settings of the test step in its editor:

TestComplete test step editor

ReadyAPI runs TestComplete (or TestExecute) through the command line. The test step’s properties help you specify command-line arguments for the run. For more information on the TestComplete command line, see the TestComplete documentation.

Property list

Besides the test step editor, you can adjust test step behavior by using its properties in the Run TestComplete Test Properties and Custom TestComplete Test Step Properties panels in the Navigator.

Run TestComplete test properties

Name

Description

Name

The test step’s name.

Description

Text describing the test step.

Execution result

The TestComplete exit code indicating the test run result:

  • 0 – Success (no errors or warnings in the log).

  • 1 – Warnings in the test log.

  • 2 – Errors in the test log.

  • 3 – The test failed to start because of an error. See the TestComplete documentation for possible causes.

There are also other exit codes. For more information, see the TestComplete documentation.

Result description

The text describing the test result. It corresponds to the Execution result value.

Test runner

Specifies the product – TestComplete or TestExecute – and its version. Usually this property is set automatically, when you specify a test runner by using the Test runner drop-down list. If you do not have TestComplete or TestExecute installed on your current computer (for example, when you use Linux or Mac) you have to specify a test runner manually. To do this, enter the name of the runner and its version (for example, TestComplete 11) in the Test runner property. During the test run, ReadyAPI finds the specified test runner and uses it to run the test step.

Custom TestComplete Test Step Properties

Values on the Custom TestComplete Test Step Properties tab are available to other test steps in your project. For instance, you can verify these property values with the Assertion test step, or check them and change the execution flow with the Conditional GoTo test step. To learn more, see About Properties.

This tab contains the following properties that provide access to the request and response data:

Test step results

Test Step Result

Condition

PASS

TestComplete tests were executed successfully, and the Execution result property is 0 or 1.

The latter works only if the Warning as error property is disabled.

FAIL

TestComplete tests failed, and the Execution result property differs from 0 and 1.

If the Warning as error property is enabled, the Execution result of 1 is also considered to be a failure.

For the result value’s description, see the Result description property.

More information

Find more information on the TestComplete and TestExecute command line and exit codes in the TestComplete and TestExecute documentation.

See Also

Publication date: