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

Sprint Scheduling: A Guide to Your Agile Calendar

Agile sprints can be a powerful, productive and collaborative event if managed properly. However, when neglected or set up incorrectly they risk becoming chaotic and inefficient. Crafting an effective schedule for your sprint is essential to ensure the success of your...

What is Enterprise IT Intelligence?

We have all heard of the term Business Intelligence (BI), coined in 1865 (in the "Cyclopaedia of Commercial and Business Anecdotes") and described more recently by Gartner as “an umbrella term that includes the applications, infrastructure and tools, and best...

Database Virtualization and Ephemeral Test Environments

Introduction: Why This Matters Across every industry, enterprises are being asked to do more with less. Deliver digital services faster. Reduce costs. Strengthen compliance. And achieve all of this without compromising resilience. Yet despite significant investment in...

IT Environments: What Are They and Which Do You Need?

The IT landscape is rapidly changing, with companies becoming increasingly distributed, cloud-driven, and agile. In order to minimize complexity and ensure operational efficiency, it’s critical to maintain full visibility and control over all your IT environments....

Self-Healing Applications: A Definition and Guide

Traditionally, test environments have been difficult to manage. For one, data exists in unpredictable or unknown states. Additionally, various applications and services contain unknown versions or test code that may skew testing results. And then to top it all off,...

What is Enterprise Architecture Management (EAM)? A Guide

Organizations operate in an increasingly complex digital environment. Business leaders want to move quickly, innovate, and meet customer expectations, while IT leaders need to maintain stability, security, and scalability. This kind of organizational friction can be...