In TestComplete, you can create and edit issues stored in Microsoft Visual Studio Team System or Mozilla Foundation Bugzilla issue-tracking systems. Using TestComplete dialogs you specify the login, password, computer name and other parameters needed to connect to the desired issue-tracking system; TestComplete will then store these settings into a template and automatically generate a method of the IssueTracking
object that will create or open for editing an item in the selected issue-tracking system. To create an item (or to modify it) you simply call this method and pass data to be stored to item fields, via method parameters.
Of course, you can write a script that will connect to a needed issue-tracking system via COM and perform all the required tasks from scratch. However, this approach requires you to know the internal structure and internal objects of the desired issue-tracking system. The approach offered by TestComplete is more convenient since you do not have to know the internal structure of the desired issue-tracking system: all the options are set up visually through TestComplete dialogs. You only call the appropriate method of the IssueTracking
object.
This section describes how to create and use issue-tracking templates.
In This Section
About Issue-Tracking Templates
Working With Issue-Tracking Systems - Requirements
About the CreateWorkItem Template
Creating Issue-Tracking Templates
Using Issue-Tracking Templates From Tests
Connecting to Your Issue-Tracking Database
The Log Was Exported to an Issue Successfully
Integration With Issue-Tracking Systems - Troubleshooting
Related Topics of Interest
In addition, TestComplete includes script extensions that provide support for the following issue-tracking systems:
-
Atlassian JIRA
-
Mozilla Bugzilla
-
SmartBear QAComplete
-
Axosoft OnTime
Note: This extension is deprecated and disabled in TestComplete by default.
For these issue-tracking systems, you can create issues only from test results. In other words, you can create a bug report for the whole log of the test run or for any of its child log, and post this report to the issue-tracking system directly from the test log.
Creating Issue Reports for Test Results