Create and Configure XAML Build Definitions (Run TestComplete Tests as Part of a Test Plan)

The computer where the team build is created and configured must have one of the following Visual Studio versions with Team Explorer component installed:

• Visual Studio 2017 (Community, Enterprise or Professional).

• Visual Studio 2015 (Community, Enterprise, Professional, or Test Professional).

• Visual Studio 2013 (Community, Ultimate, Premium or Professional).

• Visual Studio 2012 (Ultimate, Premium or Professional).

• Visual Studio 2010 (Ultimate, Premium, or Professional).

The Visual Studio version to be used depends on your version of Team Foundation Server. See the Requirements and compatibility article in the MSDN library.

Important: To create XAML build definitions in Visual Studio 2015–2017, you must have a XAML build controller installed and configured. To learn more, see the Continuous integration and deployment section in the MSDN library.

1. In Visual Studio, open the Team Explorer panel (if it is hidden, select View | Team Explorer from Visual Studio’s main menu to display the panel) and connect to your team project.

2. In Team Explorer, click Builds, and then click a build definition you want to configure to run TestComplete tests or click New Build Definition to create a new definition.

3. If needed, in the General tab of the window, specify the build definition name and description.

4. In the Trigger tab, if needed, you can specify the event that will initiate the build. By default, team builds are run manually.

5. In the Source Settings tab (for Team Foundation Server 2013) or in the Workspace tab (for Team Foundation Server 2010–2012), configure your build definition to get the needed files from your source control:

   If You Use Team Foundation Version Control

   • Map the source control directories that store your Visual Studio test project and TestComplete projects to the appropriate local directories on the build computer:

     

     Note:

     Keep in mind that the test project stores the relative path to the TestComplete project. When mapping the TestComplete source control path, make sure to select a local folder on the build agent to keep the relative path specified in the test project valid.

   If You Use Git (For Team Foundation Server 2013)

   • Specify the Git repository and the branches that store your team project files.

     

6. In the Build Defaults tab, specify the build controller that will be used to process the team build:

   

   In the Staging location section of the tab, specify the way the build process will store the output files and logs:

   • To copy output files and logs to a shared folder on the build server, click Copy build output to the following drop folder and specify the UNC path to the target folder. Make sure that the Build Server can access the folder.

   • (For Team Foundation Server 2012–2013) To copy output files and logs to a folder in the version control, click Copy build output to the following Source Control folder and specify the path to the folder.

7. In the Process tab, specify the details of the build process:

   In the Build process parameters table, expand the Build node. In the Project box, specify your Visual Studio test project containing your TestComplete tests (for information on how to create a project, see Preparing Visual Studio Test Projects for Running TestComplete Tests).

   

8. Save the changes. Your build definition will be displayed on the Builds page in Team Explorer.

After you create a build definition, start it to create a team build instance to be associated with your test plan. See 5. Create a Build Instance.