Kubernetes has changed the way we think about running container at scale. So far, developers and operations teams enjoy working with it as it enables agile, springy delivery of their applications in the cloud and beyond.

But what does it really mean to have Kubernetes as a container management system for the QA team, and how can they do the best use of this technology?

In this article we will respond to those questions. More specifically, we will explain what has changed and what & # x27; s different in term of examine workflow. We will see that in essence, software testing hasn ’ t really changed, but the execution model has gone to the next stage, so testing teams postulate to adapt and move forward with a new mindset.

Kubernetes and essay

Software testing supply an objective sight of how package deport in real time and how much it array with business necessity. Note that this description perform not mention anything about containers or container orchestration systems (orcloudor any similar term), and there is a reason for that.

As antecedently discussed,containers do not change functionality, so subsequently, any container management scheme that works on top of container maintains that truth.

What has vary is the execution framework of the different types of testing. As each type of testing (unit, integration, system) requires different setup and environment and configuration argument, it direct clip and effort to automate those stages. However, with Kubernetes, we can hold a program that scales ground on our needs and demands. We can leverage that to incorporate more advanced screen scenarios such as chaos technology or A/B prove on real production sites, so as to reduce hazard and get our systems more resilient to failure.

Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

How Kubernetes works with software testing

Kubernetes helps with software testing in many ways. I ’ ll excuse the most useful ones.

CI/CD Automation

First and foremost, as Kubernetes grant us to spin up a number of container instances with different scale policies, it ’ s a perfect candidate for CI/CD jobs and activities, and it ’ s widely used in product. For example, in our surround, we created cod that run Jenkins striver for every commit or PR submitted, and at the end of each job, they are stop. Kubernetes make it easy to submit jobs (and let it find the way to complete them).

So if you have a suite of automated trial and scripts, they can be box in containers and run as part of a build pipeline against your deployment containers, thus producing more ordered answer. In addition, tests can be based on specific parameters such asheadless: firefox and headless: chromefor runningheadless try scenarioson Firefox and Chrome respectively. These can be run in parallel expend Kubernetes jobs, thus reduce their running time.

Short-lived QA Environments

QA teams are more than happy to experience identical production environs at their disposal for try aim and automation. With Kubernetes & # x27; forward-looking container instrumentation capabilities, we can create whole test environments that share the same manifest with the product situation.

For illustration, in our line of work, we hold up several environments, such as proof, pre-production, release-user-acceptance, and so on. Not all of those environments are up all the time, and in the yesteryear, when we needed to dedicate modification to production, we manually provisioned them using script and migrated a portion of production data to test the latest requirements. Now, using Kubernetes and Terraform, we apply the production apparent, and we can spin up a new cluster for running validation tryout with no interruptions. At the end of each loop, we ruin them, cleaning up residual files and asset.

Shift-Left Testing

There is an ongoing motive to push examine functionality toward the early stage of maturation so that serious issues are identified and decide before we push to production. This is where things can get wily.

You see, the development teams experience their own workflow that dictates how well a especial piece of engineering can assist them with their work. If we want to inflict a special workflow, such as a new examine stage to run after each commit, then it ’ s best if it offers instant feedback and has detailed information about the number. The developer ’ s ability to multiply an issue accurately is the first crucial step towards interpret it and fixing it.

Kubernetes here can aid with the correct purpose and scope. Maybe running a total Kubernetes cluster in a local machine would not be hardheaded, but if testers and developer have a shared cluster that is tailored for easy debugging and examination, then they can both benefit from it. When a tester logs an issue, then the developer can instantly unite with the clustering and have all the information to attempt to fix it with confidence—so the QA and Dev team need to receive common ground.

Conclusion

As new tools like Kubernetes come into play, QA and validation engineers need to contain them more efficiently into their automation workflows, and tackle constriction. Yes — in the beginning, it will take more clip and exertion to migrate to that environment, especially towards shift-left testing. However, at the end of the day, the cost that we pay upfront can be regained with time deliverance and enhanced communication between developers and testers, so it ’ s totally worth it.

Theo Despoudis is a Elderly Software Engineer and an experient mentor. He has a keen involvement in Open Source Architectures, Cloud Computing, best exercise and functional programming. He occasionally blogs on several publishing platforms and enjoys creating projects from inspiration.