A look at six specific needs of a successful test-automation strategy and how relying on CI/CD tools can send you into the testing swamp of no return.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

Implementing a consistent testing infrastructure for cloud native applications is challenging. Many CI/CD tools have limited support for testing and QA, resulting in issues with consistency, test execution environments, and scalability. Running tests outside of CI/CD pipelines is also difficult. Testkube is a test orchestration platform that addresses these challenges by providing consistent tooling support, execution environments, flexibility in test execution, scalability, and a single pane of glass for test results.

Stop Running Tests With Your CI/CD Tool

Solution 1: A Test Orchestration Platform

Option 2: Manual Scripting and Duct Taping

<p>A lot of “problems” explain here are wrong. You encounter it because you maybe does something wrong.
I have use Jenkins, GitHub actions and gitlab ci, and I can easily run tests without needing to create a ticket for having specific versions, and I can run it easily without depending on the environment (that is the first point when you’re writing tests : do not depend on the os or browser or whatever…)</p>
<p>I just think this article was written to sell the product (sorry I have not take the time to check it, it is maybe free ?), but I have lose minutes reading this …</p>
