LF

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

The History of SRE

17 JANUARY, 2020 by Sylvia Fronczak Site reliability engineering (SRE) uses techniques and approaches from software engineering to tackle reliability problems with a team’s operations and a site’s infrastructure. Knowing the history of SRE and understanding which...

Securing Data by Masking

25 JANUARY, 2020 by Michiel Mulders With the cost of data breaches increasing every year, there’s a huge need for higher security standards. According to IBM’s 2019 security report, the average total cost of a data breach has risen to $3.92 million per breach. It’s no...

Top Test Data Challenges

08 DECEMBER, 2019 by Arnab Roy Chowdhury In the last few years, people have started to rely less on manual work and more on automation. Internet banking and online shopping portals are some examples of this growing trend of digitalization. Instead of going to the bank...

Release Management Explained in Depth

12 DECEMBER, 2019 by Carlos Schults The software development process today is very different from what it used to be 15, 20, or even more years ago. One of the most dramatic of such differences is undoubtedly the number and frequency of releases. Agile practices have...

Your Essential Test Environment Management Checklist

26 November, 2019 by Carlos Schults Your Essential TEM 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...

Why Is Test Data Management So Important?

18 NOVEMBER, 2019 by Carlos Schults Test data management is vital for achieving a healthy test automation strategy, yet many professionals are still not familiar with the term. They don’t know what the concept means, nor why it’s so important. But why would that be a...