Test Environment Anti-Patterns
by Niall Crawford
A common term used in the world of Software Development is the concept of Anti-Patterns.
An Anti-Pattern is basically a commonly occurring approach to a problem or task that generates decidedly negative consequences.
Examples of Anti-Patterns in the software development might be:
(1) spaghetti code i.e. code that becomes unmaintainable and difficult to extend
(2) duplicate code i.e. code that has been cut and paste and now must be changed in two places.
However, what people often forget is that probably over 80% of SDLC activity involves more than just coding and is made up of a complex fabric of different teams, processes, infrastructure, data & tools. All of which can have a hugely detrimental effect on quality, timeliness and IT spend.
With the above in mind, enov8 decided to list eight of the top anti-patterns & patterns in the world of Test Environment Management. Anti-Patterns) which cause disruption, inhibit testing productivity & cause IT Project delays.
The Top 8 Anti-Patterns of Test Environments Management
- Death by Spreadsheet
Anti-Pattern: The organisation is heavily reliant on spreadsheets to identify current systems under management, their components, versions and the projects using them. These spreadsheets often get out of date, are non-integrated across teams & regularly become unusable.
Pattern: A centralised CMDB or Knowledge Portal that all teams can use for visualisation, modelling and ongoing-management of systems, components, relationships, versions, and of course relationships.
- System Contention Hell
Anti-Pattern: Different teams “reactively” compete for the same system resources and components, causing test disruption & outages due to continual changes and re-configurations. Collaboration across projects is typically low and often results in finger pointing and arguments.
Pattern: Project requirements are identified early in the lifecycle and the correct system resources are shared with the most compatible teams. In areas of high contention, the organisation has time to provision new environments and/or re-prioritise to meet the spike in demand.
- Ninja Changes
Anti-Pattern: Developers deploy changes during operational hours, without prior notice and re-configure applications on the fly. The test teams are blind-sided, experience unusual disruption and defects arise that are difficult to recreate or track.
Pattern: All environment activity is collaborated through group calendars that highlight scheduled events and statuses. Affected teams are notified of changes, via alerts or dashboarding, that may impact their project or team.
- The Email Support Vortex
Anti-Pattern: Members across the project use email as a method to request test environment support and coordinate operational fulfilment. High volumes of emails go across different teams and fail to convey ownership, accountability or correct operational procedures. Thus, requests become overwhelming, uncoordinated and are often ignored & orphaned.
Pattern: All environments, whether production or test, need a basic level of service management to prevent operational chaos. Although not necessarily as “heavy” as production, the organisation needs “just enough” service management to ensure all requirements are captured, tracked & closed.
- Superhero Provisioning
Anti-Pattern: Deployment (data, application & infrastructure) operations are unrepeatable, manual, slow and error prone. They typically involve heroics from one or more subject matter experts and the use of “black magic”. This chaotic approach consequently results in disruption to the end users i.e. project and test teams.
Pattern: Organisations need to establish consistent tasks that are clearly documented and understood. Ideally these operations should evolve to become fully automated, “Single command line” tasks that can be exposed through “Self Service” forms.
- Manual Health Checks
Anti-Pattern: Every morning the test team will get in early to run various functional tests that ensure the application and the end-to-end business processes are working. Results are then emailed to the test teams. Process is typically time-consuming and typically can only be done once a day.
Pattern: Implementation of Test Synthetics that can automatically run at any time of the day, (scheduled or in real time) to provide immediate insight into whether the end-to-end environments are healthy. Results can be communicated via real-time dashboards and automated alerts.
- Stopping the Clock
Anti-Patterns: Testing and projects are often delayed due to the various engineering/provisioning teams not being available to service them. For example, the infrastructure team are too busy to provide more virtual test environments, the deployment team are too busy to release the latest code version and the data team don’t have time to provide more test data.
Pattern: Establishment of Self Service orchestration gateways (portals where provisioning automation is exposed & shared) will ultimately mean much of the “busy” work previously done by the Infrastructure, Application or Data team can be completed by the testers or project team themselves.
- Creative Reporting
Anti-Pattern: The test environment & release management teams spend many days (potentially weeks) per month collating and analysing non-integrated environment & release information with the intent of creating reports. Typically resulting in reports which are invariably inaccurate & untimely.
Pattern: Establish automated environment information aggregation that brings together all your IT environment & release information and generates real-time reports and dashboards that support analytics and decision making.
If you’d like to know how to avoid anti-patterns and address all the above and more, then please ask for a demonstration of enov8 Environment Manager. A complete solution for your Test Environment Managers, including features for: Visual Configuration Management, Project Demand Management & Test Environment Bookings, Environment Calendaring, Service Management, Self Service, Test Synthetics, Environment Dashboarding and Automation Integration & Orchestration.
About Enov8: Enov8 are the world leading providers of IT & Test Environment Management & Holistic Release Management solutions. Through using enov8’s extensible platform, Ecosystem, organisations can uplift their understanding and management of their computer systems and end-to-end IT fabric. With the intent of uplifting Environment & Release Operations, Streamlining IT Projects and reducing associated Infrastructure, License & Service costs.
19 FFEBRUARY, 2021 by Carlos Schults "You can't improve what you don't measure." I'm sure you're familiar with at least some variation of this phrase. The saying, often attributed to Peter Drucker, speaks to the importance of metrics as fundamental tools to enrich and...
08 FEBRUARY, 2021 by Zulaikha Greer Data is the word of the 21st century. The demand for data analysis skills has skyrocketed in the past decade. There exists an abundance of data, mostly unstructured, paired with a lack of skilled professionals and effective tools to...
04 JANUARY, 2021 by Ukpai Ugochi Have you ever wondered what would happen if you mistakenly added bugs to your codes and shipped them to users? For instance, let's say an IT firm has its primary work tree on GitHub, and a team member pushes codes with bugs to the...
07 DECEMBER 2020 by Daniel de Oliveira In today’s application-based world, companies are releasing more applications than ever before. Software delivery life cycles are becoming more complicated. As a result, large companies require hundreds and even thousands of test...
19 NOVEMBER, 2020 by Michiel Mulders What Makes a Good Test Data Manager? Have you implemented test data management at your organization? It will surely benefit you if your organization processes critical or sensitive business data. The importance of test data is...
22 October, 2020 by Louay Hazami Data privacy is one of the most pressing issues in the new digital era. Data holds so much value for normal internet users and for all types of companies that are looking to capitalize on this new resource. To keep data anonymous and...