Blog - The Test Environment Pizza

The Test Environment Pizza

10

JULY, 2017

by Niall Crawford (Enov8 Director/CTO)

I had an “interesting” chat with a potential client this week. The conversation started normally with myself and my colleague going through the benefits of our Test Environment & Release Management solution, and then continuing to a “show and tell”. However, I could tell the client was somewhat distracted and had something “greater” on their mind.

So, I probed slightly & the vision became apparent:

“We want our Projects to Self-Service the Test Environments”

“OK”, I said, “can you provide me an example of which Environment?”

“Yes … A Test Environment for Payments”?

“OK”, I said, “a bit like ordering a Pepperoni Pizza online?”

“Yes, that’s right” said the client enthusiastically.

“OK! Stop the bus”, I said, “Three simple questions” “Question ONE, do you know what your Payments Environment & Systems looks like?” Answer: “Not really, we have some Spreadsheets & Wiki documents but they might be out of date”. “Question TWO, are your current Infra, Data & Applications operations documented?” Answer: “It depends on the team, I believe some do and some probably don’t”. “Question THREE, can you currently create this platform from an Automate Script?” Answer: “I think the Infrastructure guys have some Recipes & Scripts for MS SQL”. Note: The latter answer amused me as there were about 150+ components, including Mainframe. I find it somewhat crazy today, that IT Management and supposed “Subject Matter Experts” are suggesting this kind of nonsense and suggesting it seriously. I mean, sure if your environment and systems are simple enough you could offer complete automation and self-service. But they probably aren’t! Instead they probably consist of a complex web of components, relationships, processes and architectures that are poorly understood and out of date. If an organization wants to establish Self Service Test Environment Management, then I’d offer this: “Understand your ingredients & learn how to cook first”. It might sound a bit boring. But it is 101 Environments Management. You can never expect to automate or self-service that which you don’t understand.

Relevant Articles

Smoke Testing: A Detailed Definition and Guide

In the realm of software development, ensuring the reliability and functionality of applications is of paramount importance. Central to this process is software testing, which helps identify bugs, glitches, and other issues that could mar the user experience. A...

What is Observability? A Foundation for SRE

Site Reliability Engineering (SRE) is a methodology for building and maintaining large-scale, highly available software systems. It involves applying software engineering practices to operations in order to increase reliability, reduce downtime, and improve the...

What is Ansible? A Detailed Guide for Dummies

As IT & Test environments become increasingly complex and dynamic, IT professionals need tools that can help them manage the complexity and ensure consistency across systems. Ansible is designed to address these challenges. In this post, we’ll provide an...

Database Virtualization Tools: 9 to Know About in 2026

Organizations evaluating database virtualization tools are usually trying to solve a very practical problem: how to give teams fast, safe access to realistic data without copying production databases over and over again. Whether the driver is test automation,...

Enterprise Release Management: A Comprehensive Guide

Enterprise Release Management (ERM) is a set of end-to-end practices that enable large organizations to effectively manage software releases. ERM is uniquely designed for the challenges of multiple teams building and releasing software simultaneously. ERM establishes...

Your Essential Test Environment Management Checklist

“Test Environment Management Checklist.” Yep, that sounds like a mouthful, but don’t let that discourage you. The idea here is quite simple—adopting a checklist to evaluate the soundness of your test environment management approach. Even though the idea sounds simple...