3. CI/CD Configuration in Avo Assure

Why was this developed?

The previous version of Avo Assure, CI/CD, was a complicated task for the user to operate (Ex: test case automation, work with pipeline tool) for any project.Now, CI/CD enables shipping code changes more quickly and consistently. Moreover, it supports test case automation and works with pipeline tools. So, to automate the testing phase of CI/CD, we Integrated CI/CD with the Avo Assure tool.

How does it look?

Create Execution profile

Execute Via CI/CD

How does it work?

CI/CD comprises continuous integration and continuous delivery or deployment by automating CI/CD phases as builds, testing, and deployment.CI/CD enables shipping code changes more quickly and consistently. Moreover, it supports test case automation and works with pipeline tools. So, to automate the testing phase of CI/CD, we Integrated CI/CD with the Avo Assure tool.

1. The user has to click the Execute button from the Avo Assure home page, as shown below.

2. Execution Profile home page will display, as shown below. Note: CI/CD is applicable only for the web application project type.

3. The user has to select the project name from Project Name drop-down box, as shown below.

4. The user has to click the Create Profile button to create configuration, as shown below. Note: Configuration creation will be a one-time process.

5. Create Execution Profile window will be displayed as shown below.

6. The user has to enter the profile name in the Enter Profile Name box, as shown below.

7. The user has to select the required type of module from the Execution Table, as shown below.

8. The user has to click the Normal Execution radio button to select normal execution modules, as shown below. Note: The modules assigned as normal execution are displayed in the execution table.

9. The user has to click the Batch Execution radio button to select batch execution modules, as shown below. Note: The modules assigned as batch execution are displayed in the execution table.

10. The user has to click the E2E Flow radio button to select end to end execution modules, as shown below. Note: The modules assigned as E2E execution are displayed in the execution table.

11. The user has to select the agent from Avo Agent/Avo Grid drop-down, as shown below. Note: Admin will create Avo agent from the admin screen. While creating the agent, the user will provide the number of Avo Assure Client instances then the Avo agent will take care of Avo Assure Client instances.

Avo Agent:

A group of Avo Assure Clients makes Avo Agent. There is no need to wait for the availability of another Avo Assure Client because Avo Agent will take care of the Avo Assure Client.Avo Grid:Avo grid is a combination of Avo agents which has groups of Avo clients.

12. The user has to select the browser from the Select Browser drop-down, as shown below. Note: From the drop-down list, the user can select multiple browsers.

13. The user has to select the integration from the Integration drop-down, as shown below. Users can also select any Integration type, including qTest, ALM, and Zephyr. Note: System will update the user test cases in the respective test management tool.

14. The user has to select the Execution Mode according to the user requirements as shown below.

Non-Headless:

All the functionalities are visible when the user executes on the browser, for example, opening the browser, tabs, loading the pages, etc.

Headless:

All the functionalities will execute in the backend in headless mode, which is invisible to the user.

15. The user has to click the Save button, as shown below.

16. Once the user saves the execution profile, the system will display a toast message and the configuration will appear in the list as shown below.

17. The user has to click the CI/CD button, as shown below.

18. When the user clicks the CI/CD button, Execute via CI/CD window will display, as shown below.

DevOps Integration API url and DevOps Request body:

Using these two parameters, the user can integrate this DevOps functionality with CI/CD pipeline.Execution Type:

• Asynchronous:

It will give you the response as soon as you execute your execution and will not wait until your execution is completed.

• Synchronous:

It will not give you a response and will wait until your execution is completed.

Through CI/CD Pipeline

1. The user has to Login to any CI/CD Pipeline like Jenkins, Azure DevOps, etc.

2. The user has to pass the DevOps Integration API url and Devops Request Body parameters to CI/CD Pipeline (Ex: Jenkins) as shown below.

3. The user has to select existing job from the Jenkins Dash-Board, as shown below.

4. The user has to change the configuration and enter the DevOps Integration API url in HTTP Request as shown below.

5. The user has to enter the DevOps Request Body parameter in Request body, as shown below.

6. The user has to click the Save button, as shown in below.

7. The user has to click the Build Now button to start the Execution in CI/CD Pipeline (Jenkins), as shown below.

8. Once the Execution is done, the system will save reports in Console Output, as shown below.

9. If the user wants to view the report again, that report will be available on the Avo Assure report page.

How can I get this?

If the user upgrades to the latest version of Avo Assure to 23.1.0, this feature will be available automatically.