Some of the common tools (or features) you'd require as part of implementing a Test Environment Management capability:
- Environment Knowledge Base
- Environment Booking System
- Environment (Infrastructure) Orchestration Tool
- Build & Deployment Tools / Continuous Integration Tools
- Infrastructure Configuration Tools
- Service Virtualization
- Environment Shakedown Tools
- Service Support Tools (Incident & Change)
- Environment Health Dashboards
Ultimately a number of different tools are likely to be used in support of your DevTest environments (e.g. Jenkins for app builds, Puppet for infrastructure configuration, CA Lisa for service virtualization, Remedy for ITSM, Informatica TDM for ETL).
The biggest challenge however is that these solutions are often disjoint and information not integrated, so there is often great value in larger organisations leveraging end to end Test Environment Governance and Orchestration platforms (for example Enov8, Omniumx or Plutora) opposed to struggling forward with traditional & archaic methods like spreadsheets.
By investing in a Test Environment tool, you will have a Single view of all test environments (& data) and a place to collaborate on and view key environment information & behavior including identifying environment configurations, environment bookings, allocation, environment activities & schedules, service support needs, team contention and health.
And ultimately uplift visibility, quality, availability, and utilization of your environments by reducing disruption, controlling costs, standardizing operations and avoiding IT project delays.
Read more: Test Environment Management Tools Compared.