A Systematic Review on AI-Driven QA Automation: The Next Normal for Continuous Testing

1. Introduction

When the historians of the future get around the commerce of our times, they are sure to garner overwhelming evidence around the appeal for artificial intelligence and machine learning. The way these two technologies have dug their heels into every possible sector in today’s global market is a revolution in itself. For IT and digitalization industries, in particular, the phrases “DevOps” and “continuous testing” are now finding themselves inseparable from the conversations around AI- and ML-based automation strategies. If anything, it already seems a bit late to expand that conversation to accommodate QA automation.

As new technology is introduced, companies, though reasonably skeptical, are beginning to explore and adapt them against the unique demands of consumers. By implementing safe and efficient automated programs for quality assurance, they are already ensuring minimal downtime and uncompromised service experience for their customers. Continuous testing has become synonymous with the QA strategies in most of the DevOps pipelines. Therefore, it only makes sense to bridge the benefits of continuous testing with the potential enrichments of AI-driven automation. Through the course of this article, we will discuss the various aspects of this bridge, including its relevance, necessity, and aftermath for the world that is already going through its fourth industrial revolution.   

Creating Happy Customers With DevOps in 8 Hours or Less [Report]

We recently ran a survey against the software testing community to understand the adoption of modern development practices and its impact on testing.

One of the things we wanted to take away from this survey was being able to identify effective DevOps practices from harmful ones. We based the success criteria on team satisfaction and customer happiness.

DevOps Radio: Seeking Progressive Delivery, Debunking DevOps Hogwash

James Governor, analyst and co-founder of RedMonk, sat with Sacha Labourey at DevOps World | Jenkins World to catch up on software development and deployment and discuss which companies were doing it well. Before they tackle the future of DevOps in Episode 44, they revisit the past (think: Sacha's JBoss days) and what James admits is not his finest moment as an industry analyst in regard to some "hogwash" on the decoupling of open source.

From there, they dive into a new-ish concept with a newer title — progressive delivery. James shares his perspective on the interaction between IT and the business if you decouple deploy from release. He notes one needs to look at the bridge between what an enterprise customer and what web companies are doing. His solution? Train the people in organizations first, or at least give IT the green light to keep deploying software and services, but let businesses decide when to activate it. It's not enough to just spin the IT wheel faster. If organizations want to have an impact loop, they need to involve the business stakeholders that understand the users of the service, and how they should be integrated into the process.