Below are key points to which you should pay attention when integrating TestComplete tests into Visual Studio and Visual Studio Application Lifecycle Management tools:
-
When preparing a TestComplete project suite for integration:
-
Share the folder that contains your TestComplete project suite or store all project suite and project files in source control.
-
Make sure that TestComplete tests run as expected on the computer where the builds will run or in your lab environment.
-
-
When creating a Visual Studio test project:
-
To make sure that the path to the TestComplete project suite remains valid after the test project is placed in the build’s drop folder, place the project suite in a shared network folder or create custom build steps that will copy the project suite to the desired location.
-
In Visual Studio 2010, create a special test list and add the needed TestComplete tests to that list.
-
Add your Visual Studio test project to a source control.
-
-
When creating team builds or releases:
-
Specify the test list or modules containing the needed TestComplete tests.
-
Make sure that your build agent or test agents are running as an interactive process (not as a Windows service) so that TestComplete can interact with the desktop and with the tested application’s UI.
-
-
When configuring a test plan:
-
Link your TestComplete tests with a test case in your team project.
-
Associate the build containing TestComplete tests with your test plan.
-
-
When deploying reports:
-
Create a Report Server project and specify the appropriate connection parameters for it.
-
The TargetReportFolder property of the created report project must specify the team project name.
-
The TargetServerURL property of the created report project must hold the string
http://<your_server_name>/ReportServer, for instance,http://tfs-server/ReportServer.
-
See Also
Integration With Visual Studio Application Lifecycle Management