DevOps Testing: Best Practices Using Alibaba Cloud

By Shantanu Kaushik

We have already discussed the DevOps methodology using Alibaba Cloud in our previous posts, DevOps for the Cloud Part 1 and Part 2. Now, let’s talk about the best practices of DevOps testing using Alibaba Cloud.

Building a Successful DevOps Testing Strategy

This is the very first step to defining a pipeline that is suitable for your software delivery. From new application software to software already in place with traditional delivery models, defining a DevOps testing strategy will enable a faster channel for development, delivery, and updates. This will further enhance business productivity. If you are upgrading your delivery pipeline from a traditional approach, this will also take care of any bottlenecks you may have faced previously.

Attaining successful deployment and maintaining it for all the releases or sub-releases of your software is an essential practice. Alibaba Cloud DevOps solutions integrate its testing environment within the CI/CD practices. Let’s see how it works using the diagram below:

Kanban | DevOps

Visual Representation of Kanban

Kanban increases the overall workflow since it highlights each step with a visual representation. You can easily make out any bottlenecks or other issues that may be affecting the performance of your total delivery process. Different teams working within the cycle can collaborate using Kanban to help achieve a better DevOps workflow.

Just a quick reminder — Alibaba Cloud Academy offers excellent courses for you to master DevOps and follow a better learning path. Be sure to check it out if you’re interested!

Best Practices | DevOps Testing

Automate to Achieve

Alibaba Cloud DevOps CI methodology suggests that testing should be automated to achieve and fix machine errors and other issues. Although, when it comes to checking for release readiness and usability or user operations, testing should be kept on the human side.

When it comes to Quality Assurance (QA), you need to consider using all aspects of DevOps. Development, integration, testing, and deployment, every aspect should be carefully separated and checked for issues that users might face.

After achieving maturity in your automation practices, the whole approach towards DevOps automated cycles will grow from just a collection of errors and their respective solution to a pan-system data analysis that will present a layout with the worst clogs in your system. It will also outline the best working modules within your system.


Gathering viable test data proves to be another vital component when it comes to DevOps testing practices. Centralized QA data can provide a better understanding of module viability and effectiveness. This can produce an overview of your testing practice across the delivery pipeline. In case your tests are failing or taking longer execution times, this particular module can be marked for review.

This documentation must include all of the changes and why they were made. The three important things to document with your test data are success/failure listings, how it succeeded/failed, and what steps were taken to fix the failures. Differences in delivery or performance, testing times, and data are some of the key metrics in these situations.

Continuous Testing

This is a way to allocate the testing budgets and testing to meet the demand. This can also help control or regulate the release frequency of your software iterations. Continuous testing leads to an error-free environment and takes care of situations that might arise due to human error.

The Alibaba Cloud DevOps model suggests continuous integration and testing practices to the level where almost every module in the cycle is either automated or the user can use a testing automation tool to achieve an error-free cycle.


The views expressed herein are for reference only and don’t necessarily represent the official views of Alibaba Cloud.

Original Source:

Follow me to keep abreast with the latest technology news, industry insights, and developer trends.