Select Page

Test Environment Management Use Case

22

March, 2017

by Niall Crawford

Test Environment Management Use Case

We often get asked by people “What is TEM (Test Environment Management), well for those of you looking for a quick overview of Test Environment Management, here is Use Case we developed as way of explanation.

In a nutshell, Test Environment Management “Use Case” it is about ensuring the Environment Managers, Project Managers, Test Mangers, Developers, Engineers & System SMEs (Subject Matter Experts) collaborate to ultimately ensure Environment transparency, readiness and ultimately stability of your environments across the life-cycle.

And this “Use Case” can all be described in 9 simple steps:

Step#1 Know what your IT Environments look like. As we see it, if you can’t understand (and model) your Production or Test environments your chances of managing them effectively are next to negligible.

Step#2 Understand & Capture the demand and usage of your Test Environments. Demand will initially come from the overarching Portfolios & Projects and early insight will ensure you can proactively plan, coordinate and provide fit for purpose environments in a timely fashion.

Step#3 Understand & Capture the demand and usage of your Development & Test teams (via Test Environment Bookings). And align these requirements back to definable SDLC phases and operations like SIT & User Acceptance Testing.

Step#4 Ensure all your Test Environment activity & operations are planned, centralized and communicated. Key people involved might include the system owner, the infrastructure, application and data engineers involve in provisioning and those involved in testing quality and health.

Step#5 Ensure your customers (the purveyors of your environment) are continually supported. Ensure you establish some fundamental service management so incidents can be dealt with quickly and requests for change & release can be adequately controlled.

Step#6 Coordinate your day to day environment events and release operations using effective scheduling and standard operating procedure (run-books).

Step#7 Look to streamline the most common operations (e.g. system shakedown) by replacing manual methods with automated tools & methods.

Step#8 Analyse Environment Activity, Health, Usage & Availability & produce reports to share with the team and your stakeholders.

Step #9 Continually learn & evolve by using the centralized information at your disposal, look for opportunities to reduce your test environment footprints, streamline your release operations, streamline your DevOps activities and establish methods to reduce IT environment disruption.

Ultimately with the intention of:

  • Operational Uplift across DevOps & Test
  • IT Cost Optimization
  • Reduced DevTest Disruption
  • Reduced IT Environment Spend &
  • Accelerated Delivery (Time to Market)

About enov8: enov8 is a specialist software engineering house that has established the world’s leading IT & Test Environment management platform. A solution that addresses all the requirements in the above use case and much more through a broad range of supporting functions including modules for Environments Management, Visual Configuration Management, Service Management, Enterprise Release Management, Release Management & Resilience.

Relevant Articles

DevOps versus SRE – Friend or Foe

19 MARCH, 2020 by Michiel Mulders SRE vs DevOps: Friends or Foes? Nowadays, there’s a lack of clarity about the difference between site reliability engineering (SRE) and development and operations (DevOps). There’s definitely an overlap between the roles, even though...

Site Reliability Engineering (SRE) Top 10 Best Practice

06 MARCH, 2020 by Arnab Roy Chowdhury Top 10 SRE Practices Do you know what the key to a successful website is? Well, you’re probably going to say that it’s quality coding. However, today, there’s one more aspect that we should consider. That’s reliability. There are...

What Is Data Literacy? (aka Know Your Data)

20 FEBRUARY, 2020 by Arnab Row Chowdhury   Technically, the world today has advanced to a level we never could’ve imagined a few years ago. What do you think made it possible? We now understand complexities. And how do you think that became possible? Literacy! Since...

What Is SRE (Site Reliability Engineering)?

14 FEBRUARY, 2020 by Michiel Mulders A site reliability engineer loves optimizing inefficient processes but also needs coding skills. He or she must have a deep understanding of the software to optimize processes. Therefore, we can say an SRE contributes directly to...

Data Compliance: What It Is and Why You Should Care

07 February, 2020 by Arnab Roy Chowdhury Do you remember what Uncle Ben said to young Peter Parker? “With great power comes great responsibility.” The same applies to companies. At present, businesses hold a huge amount of data—not only the data of a company but also...

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...