Containers assist you deploy apps faster and integrate best. But containers only work well if you have an efficient examination strategy in place.

At many administration, this is not the case. Even though container get been around for a long clip (Docker was introduce in 2013, and former container platforms were around earlier than that), testing strategies for containers have not germinate as rapidly as containers themselves.

Fortunately, by borrowing some mind from Infrastructure-as-Code (IaC) tools, and direct advantage of an automated quiz grid like Sauce Labs so you don ’ t hold to keep your own examination base when testing containerize apps, it ’ s possible to construct effective software test strategy for Docker containers. I explain how in this post.

Infrastructure-as-Code Testing Strategy

Let & # x27; s take an existing application using IaC to deploy an coating on a developer, staging, or production environs. The uninterrupted desegregation (CI) pipeline has several testing guards at each stage of the pipeline. The continuous testing approach will run static analysis, unit, integration, performance, security, and more on IaC against the coating code. As you can see, this perform a great job of screen an covering, but falls short when try container-based Dockerfiles.

Entering the World of Containers

How could this container-based shift impact the team? Arguably, one of the most critical components of a package application is a quotable and disposable infrastructure with examine. The container-based application has no exceptions. This only means we need to ask some of the following questions when entering uncharted territory.

• How do we run static analysis on Docker container images?

• How would we run subsist covering tests, such as unit, Selenium, and more?

• How should we quiz a Docker container after a Docker build?

• How do we direct scanning Docker container image for security vulnerability?

• Are there any security concerns when using public Docker containers?

• Does my existing CI solution work with containers?

  SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

Let & # x27; s start devising a testing scheme for container-based applications.

Creating Test Docker Images

If you are thinking to yourself, “ Why don ’ t we just use Docker to run application trial? ”, then you are a step ahead of the game! More or less, the Docker test setup revolves around create a tryout Docker image during build clip based off the application Docker icon, and running tests inside the test container. That let all the dependency management to move inside the exist Docker container, and for the tests to be self-contained.

Yes, Dockerfiles Need Static Analysis

An important pre-check validation adds a linter (Dockerlint) to help build consistency and best practices for Dockerfile ontogeny. To conduct it a step further, we should guess about scanning our Dockerfiles for security vulnerabilities. We want to verify and report that the Dockerfiles are free from protection vulnerabilities and protection exposures. You can find protection scanning with an opt-in pick for private repos on Docker Cloud and Docker Hub for a price. Clair and Dockscan are possible open germ selection for free.

Server Validation

After containerize the covering apply & # x27; docker build, & # x27; we need to run the application container to run server integration examination. This allows us to verify the coating waiter configuration to secure we are coherent and dependable after running Docker container. The testing proves that the correct packages were installed, configure aright, and tested on various program (CentOS, Ubuntu, and more). Personally, I am forever on the lookout for instrument and technology that assistant my squad progress high-quality applications. Goss, Dockerspec, RSpec and ServerSpec are a small lean of server testing solutions.

Continuous Integration or Delivery

Your continuous testing strategy for CI/CD with container should include a standard to pick up the test containers after you are done using them. To cancel the container after the test is complete, add the -- rm flag to the & # x27; docker run & # x27; bidding.

& # x27; docker run -- rm -u root $ {testImageTag} acceptance-test & # x27;

Using Containers on a Test Grid

Before closing, it ’ s worth noting that container are not a examine nostrum. They can improve your existing trial workflow, but they are not a substitution for it.

This is because testing exclusively using containers would expect setting up your own test grid, which is a huge amount of work. While it ’ s theoretically possible to do this, it ’ s not a good use of clip or money.

This is why you are better off utilize a test grid like Sauce Labs, which doesn ’ t require you to own and manage your infrastructure. You can notwithstanding use container in junction with the Sauce grid, but you don ’ t feature to set up all of the base to go with it.

Conclusion

We should virtually always be testing our Dockerfiles and application as described above. It allow us to take the colony from the physique server into the container, and besides create it potential to screen our Dockerfile and the covering inside the Docker container simultaneously. This frame-up can be applied to any type of application. # testALLthings

Greg Sypolt is a Fixate IO Contributor and a Senior Engineer at Gannett | USA Today Network, responsible for test automation solutions, test reporting (from unit to end-to-end), and continuous integration across all Gannett | USA Today Network products.

In the last two years, he has helped change the testing approach from manual to automated test across various production at Gannett | USA Today Network. To determine betterment and testing gaps, he conducted a face-to-face interview survey process to understand all the ware development and deployment processes, testing strategies, and tooling. He provides a formal education program for squad still perform manual testing that allows them to transition to machine-controlled testing.