Containers help you deploy apps faster and integrate better. But containers only work well if you have an effective testing strategy in place.
At many organizations, this is not the case. Even though containers have been around for a long time (Docker was introduced in 2013, and other container platforms were around earlier than that), testing strategies for containers have not evolved as rapidly as containers themselves.
Fortunately, by borrowing some ideas from Infrastructure-as-Code (IaC) tools, and taking advantage of an automated testing grid like Sauce Labs so you don’t have to maintain your own testing infrastructure when testing containerized apps, it’s possible to build effective software testing strategies for Docker containers. I explain how in this post.
Read More | https://saucelabs.com/blog/devising-a-testing-strategy-for-containers
Greg Sypolt (@gregsypolt) is Test Automation Architect at Gannett | USA Today Network, Fixate IO Contributor, and co-founder of Quality Element. Responsible for test automation solutions, test coverage (from unit to end-to-end), and continuous integration across all Gannett | USA Today Network products.In the last three years, he has helped change the testing approach from manual to automated testing across several products at Gannett | USA Today Network. To determine improvements and testing gaps, he conducted a face-to-face interview survey process to understand all the product development and deployment processes, testing strategies, tooling, and interactive in-house training programs.