Prepare TestComplete Project for Integration

1. Specify tests you want to run

2. Make sure that your tests can access your tested application and all files and resources required for testing

1. In TestComplete, open the project that contains tests you want to run.

2. In the Execution Plan editor of the project, create test items and specify tests they will run.

   Important:

   • Mark test items you want to run as test cases (by selecting the check box in the Test case column of the item). Only test cases can run as part of a pipeline. The TestComplete test adapter will ignore test items not marked as test cases.

     Test items can be marked as test cases depending on the type of the test that the item runs (you set it in the Execution entity column of the item):

     • Test items that run a separate test (for instance, a keyword test, or a script routine) can be marked as a test case.
     • Test items that run separate BDD scenarios are always marked as test cases.
     • Test items that run tests by tags or tag expressions are always marked as test cases.
     • Test items that run an entire BDD feature file cannot be marked as test cases.
     • Test items that run a scenario outline can be marked as test cases depending on the Treat each example in Scenario Outline as a separate test case option of your project. If the option is enabled, such items cannot be marked as test cases.

   • Nested test items (that is, test items that are the children of other items) cannot be run as part of your build or release pipeline or test plan. The TestComplete test adapter will skip such test cases.

   • Make sure that the created test cases can run independently of each other. When you run them as part of a pipeline or test plan they may be distributed among multiple agents and executed in an arbitrary order.

   

   Click the image to enlarge it.

   For detailed instructions on how to create and manage test cases, see the Execution Plan editor description.

3. Make sure that the created test items run correctly. For example, by running them on your local computer.

4. Add your TestComplete project suite to the repository of your team project.

   

   Click the image to enlarge it.

   We recommend that you do it directly from TestComplete IDE. This way, only the necessary files will be added. How to add the project suite depends on the type of the repository you use to store team files. To learn how to add TestComplete projects to various source control systems, see the Integration With Source Control Systems section.

5. If you are going to use TestComplete tests to automate Azure DevOps or Team Foundation Server test cases, link TestComplete cases to your team project’s test cases. To learn how to do it, see:

   Link TestComplete Test Cases to Azure DevOps Test Cases

   Otherwise, skip this step.

• If your projects use the Tested Applications collection to run your applications under test, make sure that the application launch parameters that the collection items specify will remain valid after your project is placed to Azure DevOps test agents.

• If your tests launch your tested applications by using hard-coded launch parameters, make sure that those parameters will remain valid after your project is placed to Azure DevOps test agents.

• If your tests use external files, for example, files that store input test data, make sure that they will be able to access them when running on your Azure DevOps test agents.

You may want to configure your pipeline to place all the needed files to your Azure DevOps test agents before you run your TestComplete tests. If the files are stored in your source control repository, configure your pipeline to place them to the needed target location on the test agent. You can also use various pipeline tasks to do this.