AIO Tests Results Publisher
Introduction
The AIO Tests Publisher Task provides yet another easy to use interface to report test results
into AIO Tests for Jira, right after the automated tests have run. The task wraps up the AIO public APIs to
import test results from TestNG/JUnit/NUnit/Robot result XML files or Cucumber.json or Newman reports. It can be used with any framework capable of generating JUnit files
like Cypress/Playwright amongst many others.
The plugin gives the following options
- to create new cycles or use existing cycles in AIO Tests
- to update existing Cycle case runs or create new execution Cycles on the fly for each run.
- to add cases to an execution Cycle
- to create new Cases in AIO Tests, if they do not exist
Getting started
Installing the plugin
AIO Tests Publisher task can be installed from the Azure Devops Marketplace.
- Login to your Azure Devops instance.
- Go to Azure Marketplace
- Now search for AIO Tests and click Get it Free
Reporting results
The plugin works as a task step, after the build steps are run.
Assuming that the tests have run and a results xml (Junit/TestNG/any XUnit framework which generates a JUnit xml report)
has been generated, the AIO Tests plugin can be used as below to report results of cases in the report XML to Jira.
Go to pipeline -> Edit
Click on the Task Assistant -> Search for AIO Tests -> Select the AIO Tests Results Publisher
Specify the authentication and Project for which run results need to be published
Choose a framework and specify the path of the file - relative to the workspace eg. /target/surefire-reports/testng-results.xml
For frameworks other than JUnit or TestNG, if results file is being generated in JUnit format, please select JUnit
Select preferences for results reporting
Specify the API Key generated from AIO Tests in Jira. Please refer Generating API Key
for more information
| Field |
Details |
| Cycle Preference |
Select between existing and new cycle |
| Cycle Title |
In case of new cycle, Cycle title will be used as the cycle title |
| Cycle Key |
If existing cycle is selected, AIO Tests cycle key eg. SCRUM-CY-121 |
| Add Case |
If checked, cases not already in cycle are added, else the cases are reported as errors |
| Create New Run |
If checked, new run is created for each case execution, else existing run is overwritten |
| Create Case |
If checked and no case exists with a matching case key or automation key, a new case is created |
| Update case |
If checked, it would update case steps in case of Cucumber, Newman and Robot |
| Report results as a batch |
If checked, a batch will be queued in AIO Tests to process the results file |
Support
For any issues or enhancements, please reach out @ AIO issue tracker.
About AIO Tests
AIO Tests for Jira is a test management tool which aims to simplify the entire test lifecycle with powerful features
like simple testcase creation and management, traceability with requirements, modularization of cases, efficient case execution,
insightful reporting and agile automation.
To learn more, please have a look at our extensive documentation.
