TestComplete + MS Release Management Automation

Hi Kevin,



Unfortunately, I am not familiar with Release Management 2013, so I cannot provide you with the exact answer, but I am pretty sure that it should be possible to integrate TestComplete with it.

What is possible with TestComplete:

-- It is possible to start TestComplete from the command line and command it to execute some given test or set of tests;

-- It is possible to start TestComplete as an automation COM object and command it to execute some given test or set of tests;

-- When test is over, TestComplete returns an exit code that indicates whether the test log contains errors/warnings or not;

-- TestComplete provides a means (test events) that make you possible to write a code that does something (e.g. communicates to your release management system) when an error or warning is going to be posted to the test log.



I don't have TestComplete's help system at hand, so I cannot provide you with the exact links to the topics that describe the mentioned functionality, but I hope that you will be able to find these topics either in the local TestComplete's help system or online at http://support.smartbear.com/viewarticle/63445/?st="0".

I was curious about this as well and found this help page. There's even an example batch file to handle show how to various exit codes.



http://support.smartbear.com/viewarticle/56560/

TestComplete.exe provides the following exit codes, which report on the results of the last test:

Exit Code	Description
0	The last test did not produce errors or warnings.
1	The last test results include warnings but no errors.
2	The last test results include errors.
3	The test cannot be run because of an error. Some typical errors are: The project (or project suite) path is specified incorrectly. The specified project (or project suite) cannot be opened because the current user does not have appropriate permissions for this. There are no selected test items to be run. A test item refers to an unavailable test (for example, a keyword test or script routine that does not exist, or a project item that is unavailable because the needed plug-ins are disabled or not installed). A project item file does not exist (for example, it could have been deleted, renamed or moved to another folder). The script contains a syntax error. The test engine also returns the code 3, if you run a project or project suite and the test was stopped with a call to the Runner.Stop method within the OnStartTest event handler. In this case, TestComplete considers the test was unable to start.
4	The test run was stopped by the timeout specified with the /Timeout command-line argument. For more information, see the Terminating Tests on Timeout topic.
1000	Unable to launch TestComplete, because another instance of TestComplete is already running, or because TestExecute is running.
-1	Unable to launch TestComplete because the license check has failed and TestComplete cannot obtain a license. You can find information on TestComplete licensing in TestComplete 10 Licensing Guide that is shipped with TestComplete. Tip: Inspect the Error.log or Silent.log files to get more information on the possible reasons of the license check failure. For more information on these files, see the description of the /SilentMode and /ErrorLogcommand-line arguments in the TestComplete Command Line topic. To resolve licensing problems, please use the Licensing Troubleshooter on our web site: Licensing Troubleshooter