User Guide 
Integration with third-party tools
Azure DevOps Services integration
Uploading TestArchitect test results to Azure DevOps Services
Integration with third-party tools
Azure DevOps Services integration
Uploading TestArchitect test results to Azure DevOps Services The requested page is not available for selected version.
Mapping test results between TestArchitect and Azure DevOps Services
This section describes possible test results mappings between TestArchitect and ADO when TestArchitect test results are uploaded into ADO.These are options that you set in the TEST MANAGEMENT window of TestArchitect’s Azure DevOps Services external tool.
| No | TA test status | ADO test status |
|---|---|---|
| 1 | Passed | Passed (default) Failed Inconclusive |
| 2 | Failed | Passed Failed (default) Inconclusive |
| 3 | Passed with Warning/Error | Passed Failed (default) Inconclusive |
| 4 | Passed with Known Bug | Passed Failed (default) Inconclusive |
| 5 | Not Finished 1 | Passed Failed Inconclusive (default) |
| 6 | Not Run 2 | Passed Failed Inconclusive (default) |
Important:
1 Not Finished occur if a test is started, but it is unable to reach the end of an automated run. An unfinished test case may result from any one of the following:
- an automation error;
- test case timeout is reached;
- execution of a terminate built-in action;
- execution of an exit test module built-in action;
- execution of an exit test case built-in action.
2 Not Run occurs when a test case is not even started.
ADO: Azure DevOps
Tel:
Email: