Import Results through Cycles Tab

Owned by APPWRK Writer
Last updated: Feb 27, 2024
5 min read

AIO Tests supports importing of the automation test execution reports through the Cycles tab of the app along with supporting it through REST calls. This article covers the options available in the app while importing results.
In this documentation, you will understand how to:

After mapping automated tests (TestNG, JUnit, Cucumber, NUnit, and Postman) to AIO tests and executing the test suite, the results file is generated. This results file can then be imported via the AIO Tests app for existing cycles as shown below.

Importing Results

Importing of results can happen from the cycle's list for any particular cycle or from the cycle details page of a cycle.

From Cycles Listing

For any cycle, right-click on the row and select Import Results.

fbsgsvs.png

From Cycle Details

When on a cycle details page, click on Import Results from the ellipsis as shown below.

Import Results Input Screen

Clicking Import Results from either of the above-mentioned places, the Import Automation Results window is displayed that shows the key of the selected cycle along with the option to upload the results.xml file (size limit - 10 MB) and choose a framework.

TestNG Input Screen

 

JUnit Input Screen

 

Cucumber Input Screen

 

 

The options available while importing are explained below:

  • Create New Run for Results: A new run is added to the case and the status is updated in the newly created run. If not checked, the status is updated in the last existing run of the case. The option is enabled by default.

  • Add cases if not in Cycle: If the cases mapped in the results file do not exist in the selected cycle then by default the cases will be added to the cycle; a run will be created for them and results will be updated on the run. If not checked, these cases are reported as errors. The option is enabled by default.

  • Create case if no key or automation key is found: If the option is enabled and no case exists with a matching case key (JUnit 5/Cucumber/TestNG) or automation key (JUnit4/Cucumber/TestNG), a new case is created and added to the cycle and status is updated in the cycle. The option is not enabled by default

  • Cucumber Only Option - Update case with scenario steps: If the option is checked, then the automated results scenario files become the source of truth and the AIO Tests are updated with changes in the scenario steps

After uploading the file and selecting the appropriate options, click on the Import button to import the results.

Import Summary

Once the file is attached and imported, a summary is generated with the count of successful imports and errors. Below is a sample import summary. Clicking on the ‘Details’ links gives additional information about the successful keys and error keys along with details.

 

 

 

Successful Imports Details

For the sample .xml file that was imported to get the above summary, the click of the Details link for successful imports is shown below. It shows the list of case keys for which results have been imported. Clicking the Details link again will close the section.

For the example below, ADP-TC-11 has been successfully imported with one run and ADP-TC-1 has been successfully imported with 6 runs (in sample .xml, ADP-TC-1 was mapped to two automated cases and one of the automated cases was invoked 5 times; resulting in 6 runs as “Create new run for results“ was selected).

Errors Details

For the sample .xml file that was imported for getting the above summary, the click of the Details link for errors is shown below. It shows the list of case keys that have errored out along with the error description. Clicking the Details link again will close the section.

For the example below, the import of ADP-TC-2 is erroneous since the case is in Under Review status and the import of ADP-TC-100 has also resulted in an error as the case key is not found in the system or it can be in draft status with someone else being the owner and thus the logged in user doesn’t have access to it.

TestNG Output

JUnit Output

Known Errors List

  1. Invalid xml: Unable to parse file. Please check if it is a valid results.xml file.

  2. <Case key> is in Under Review/Draft status. Only published cases can be added to cycle.

  3. <Case key> not found or you don't have privileges to add this case.

  4. Case does not exist in the cycle. Set addCaseToCycle if you wish to add.

  5. No case found with this automation key. Either map automation key or set createCase to true.

Cucumber Only Errors List

  1. Mapped case is a Classic case in AIO Tests. Please check mapping: case key/automation key.

  2. Case steps don't match with scenario steps. Please select 'Update cases' to force an update.

  3. Case steps in the existing run don't match with scenario steps. Please select 'Update cases' to force update and Create a New Run to get an updated version.- When a case has already been added to a cycle, and scenario steps in the imported file do not match the current run’s steps.

Cycle Details

Users can click on the ‘Cycle Details’ button on the Import Summary window to review the imported results in the AIO Tests App as shown below.

For further queries and suggestions, please feel free to reach out to our customer support service via help@aiotests.com.