User Guide Integration with third-party tools Azure DevOps Services integration Uploading TestArchitect test results to Azure DevOps Services

 Manually uploading TestArchitect test results to Azure DevOps Services

Manually uploading TestArchitect test results to Azure DevOps Services

TestArchitect test results from projects or test cases which are mapped to ADO can also be uploaded to ADO by manual means.

Ensure that you have already taken the following steps:

• Registered Azure DevOps Services with TestArchitect. (Learn more.)
• Mapped the TestArchitect project containing the test cases of interest to a ADO project. (Learn more.)
• Mapped TA test cases to ADO test cases. This can be achieved by any of the following means:

  -   Performing [manual mapping](/user-guide/integration-with-third-party-tools/automated-testing-in-azure-devops/mapping-ta-test-cases-to-ado-test-cases/) between TA test cases and ADO test cases.
  

  • Performing manual mapping between TA test modules and ADO test cases.

To manually upload TestArchitect test results to ADO:

1. In the TestArchitect explorer tree or a result list view, right-click a test result, and then select External Tool > Azure DevOps Services > Upload to Azure DevOps Services .

2. In the Select Location dialog box, specify a location on ADO that you want to upload the result to through either of the following:

   • Explicitly defining the location:

     1. Click Select a Destination Folder.

     2. Select a location that you want to upload the result to.
        
        

        Attention:
        Selecting the location that directly contains your mapping test case will minimize your results upload time. For example:
        • If your mapping test case is placed inside Action Based Testing but you select the Serial Run. In this case, will cause a performance issue.

   • By using Test Plan Settings:

     1. Select Test Plan Settings.
     2. Enter Test Plan information to query a collection of satisfied ADO test cases, and then click OK.
        
        

   • By using Test Run Settings:

     1. Select Test Run Settings.

     2. Enter Test Run information to query a collection of satisfied ADO test cases, and then click OK.
        
        

        You could also configure this setting by using arguments in execute command

3. Select the Upload attachment(s) to Azure DevOps Services check box to upload the TestArchitect test result to selected ADO test cases as an HTML file attachment. (Selectivity is determined by the field as follows).
   
   

4. Use the By Azure DevOps Services result list box to specify which type(s) of ADO test result accept an attached TestArchitect test result.
   
   

   • Passed: Upload the TA test result as an attachment if the ADO result status is Passed.
   • Inconclusive: Upload the TA test result as an attachment if the ADO result status is Inconclusive.
   • Failed: Upload the TA test result as an attachment if the ADO result status is Failed.
   Notes: 

   • The mappings between TestArchitect and ADO test result statuses (that is, how ADO interprets each TA result status) are defined during initial configuration of the TA repository’s connection to the Azure DevOps Services. (Learn more.)

   • If more than one condition is selected, they are effectively OR’d together. For example: If both Passed and Failed check boxes are selected, any TA result that has an ADO status of either Passed or Failed is uploaded as an attachment.

5. Select the format of the uploaded test result:

   • HTML: (Default) Upload the result as an HTML file.
   • Compressed (Zip): Upload the result as a zipped HTML file.
   • Automatically compress result(s) if file size > KB: Upload the result as a compressed (zipped) HTML file if the file exceeds the specified size. Otherwise, upload the result as an uncompressed HTML file.
     
     

6. Optional: To upload results as an HTML with your own view layout, select the Apply customized XSLT template check box, and then choose a location of your customized XSLT template.
   
   

   You are first required to customize the default XSLT template, which means you need to modify a set of XSL files to suit your desired view layout. (See more examples here.)

   Attention:
   When your customized XSLT is invalid, the default XSLT template, located at the {TA_INSTALL_DIR}\templates\xsl\ directory, is automatically applied.
   Notes: 
   if you are using a repository on another machine, make sure that the template you choose is accessible to the repository server under the account that starts the repository server service. It means that the template needs placing either on the repository server or in a network shared folder. Otherwise, the default template will be used.

7. Click OK.

   TestArchitect uploads the selected test results to ADO at the specified location and displays the upload confirmation message.

8. Click OK to close the confirmation dialog box.

TestArchitect test results are uploaded to ADO in the format specified in step #5.

ADO: Azure DevOps