Test Environment Management Use Case
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.
25 AUGUST, 2019 by Jane Temov Data security, The problem is scale & a lack of bees One of the biggest challenges of securing one’s enterprise data is the sheer volume. Think about it. Hundred (perhaps Thousands) of Applications, Thousands (perhaps Tens of Thousands)...
13 AUGUST, 2019 by Jane Temov So, you’ve been asked to write a “Test Environment Management Plan”? Or perhaps you just want to write a plan to baseline your current non-production processes, outline future test environment strategy and/or educate those around you. *...
02 AUGUST, 2019 by Eric Olsson Preamble Software is buggy. It's a bold claim, I know. Sarcasm aside, the battle to keep your applications up and running is ongoing. Wouldn't it be nice if you had a way to eliminate an entire class of bugs from your application?...
15 JULY, 2019 by Peter Morlion Martin Fowler AntiPattern "An antipattern is a solution that initially looks like an attractive road lined with flowers... but further on leads you into a maze filled with monsters." Since the dawn of computers, we’ve always had to...
26 June, 2019 by Justin Reynolds Gone are the days of monolithic software applications. In today’s microservices-and-continuous-integration driven world, where apps run in hybrid cloud environments and users engage with them on any device and on any underlying...
03 JULY, 2019 by Justin Reynolds Even since the agile manifesto was published in 2001, software development has never been the same. In a pre-agile world, software was released in monolithic packages every year or every two years. The agile approach to development...