Azure DevOps Plugin

Continuous Integration/Continuous Deployment (CI/CD) is a set of practices to automate the process of integrating code changes into a shared repository and then deploying those changes to production environments. Continuous Testing is an essential aspect of the CI/CD process, ensuring that code changes are thoroughly tested at every stage of development and deployment.

Azure DevOps is a suite of cloud-based development tools provided by Microsoft, designed to help teams plan, build, test, and deploy software applications efficiently. Azure Pipelines, a component of Azure DevOps, facilitates the implementation of CI/CD pipelines. It allows developers to automate building, testing, and deploying applications across different platforms and environments.

The AIO Tests Jenkins plugin provides another easy-to-use interface to report test results right after the automated tests have run, thus easing the process of reporting results to AIO Tests. The plugin wraps the AIO public APIs to import test results from Cucumber (via cucumber.json), TestNG, JUnit, Newman, NUnit and Robot files. The plugin is available for all Cloud and Data Center instances.

In this documentation, you’ll understand:

Installing the AIO Tests Publisher Task

Step 1: On the Azure DevOps Marketplace, search for AIO Tests or click here.

Open

Step 2: Click on the Get it Free button.
Step 3: Select the Organization for which the task has to be used and click on Install.

Open

Installation should proceed successfully and the following success screen is displayed.

Verify that the extension has successfully been installed in the Organization Settings.

Setting up Pipeline Task

Step 1: Search for the AIO Tests Publisher Task in the Pipeline Editor.

Step 2: Add the Authentication details:
- For Cloud Hosting: Add the API Key without the AioAuth prepend text, generated from My Settings → API Keys.

- Jira DC: Add the Jira DC URL of your firm and add the PAT Token.

Step 3: Add the Project and Cycle Preferences information. Either a new cycle can be created or an existing cycle can be reused in a build.

Step 4: Select Reporting Preferences.
- Report results as a Batch: A batch process would be queued in AIO Tests to process bigger files and a batch ID will be returned (Batches run typically every 2 minutes). The batches are accessible from the Cycle screen of the cycle being used for the build.

- File Path: Add the path of the file from the base folder. If more than one file needs to be picked, then regular expressions of *.json or * or *.xml can be used.

Step 5: Click Add. The following yaml task gets added to the pipeline.

Step 6: Trigger the pipeline. If files are found with the specified results file path, then results should be reported to AIO Tests in the cycle

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