How to Manage Multiple Test Environments in a Hyperconnected Cloud World

The advent of the cloud came to give us testing superpowers: one properly configured Kubernetes file and one can easily spin up a bunch of Docker containers that faithfully represent the production environment. However, with ease of use comes abuse, and the proliferation of test environments is beginning to be a real headache to many organizations, both in terms of management and cost. Abraham has suffered this first hand, and from his experience at the trenches a number of strategies have materialized: universal feature flags, meta-automation, and test environment rationalization. These techniques will allow you detect when you have overlapping and superfluous testing efforts, introducing the opportunity for cost savings, all while making sure your suite of tests environments remains flexible enough so as to take into account the different needs at different development stages. With these strategies you’ll feel confident that your test environments give you what you reed, but no more.