Automating the Automation – No Code ‘Environment Synthetics’
by Niall Crawford
The intention of environment synthetics is to provide ‘high-level of confidence’ applications (your system instances e.g. UAT Home Loan System) and their underlying component services (e.g. IIS, MSQL, Oracle, LDAP etc.) are operational and available for testing.
An ongoing activity that is laborious and surprisingly still completed manually in many organizations.
An approach that is suboptimal and quite costly.
As a way of example: a medium to large company.
The Cost of Manually Testing your Environment Health
- I need to test each test system (maybe production) every morning.
- I have 100 systems (each with 5 instances), that is 500 test system instances.
- The average manpower of testing each instance is 15m.
- Daily cost = 15m/60 (hour) x 500 x $100 (hourly charge rate) = $12,500 per day.
- Annual cost of manually testing health of our Test Environments
240 (business days) x $12,500 = $3M pa.
Note: This example excludes potential saving from cost avoidance due to delays & outages.
So, even without considering the saving in broader areas like delay and outage avoidance, we can see a compelling reason to automate. I think we can probably agree that some form of test automation is good.
As an example:
ROI of Building a Test Automation Synthetics Framework
- 500 Scripts
- Time to build each script originally is 16 hours (inc analysis, design, build & test).
- Estimated maintenance & execution of script 16 hours pa.
- Annual Cost of Automated Testing
500 x 32 hours x $100 (hourly charge rate) = 1.6M Year-1 ($800K Y2 onward).
- ROI (compared to Manual) = 1.6M (Year1) and 2.4M (Year2+)
Pitfalls of Test Automation
However, there are pitfalls with this approach,
- There is the cost of the tools (often expensive).
- The likelihood of resources (SMEs) being more expensive.
- The ongoing need to coordinate, build, maintain, and execute the artefacts (refer above).
- The reality that mileage so often varies due to the quality and efficiency of the resources involved.
So, can we do it better?
Well potentially yes, but it would require you to somehow displace the automation described above or potentially automate the creation of the automation. This method would displace automation build costs, resourcing costs, and ensures standardisation.
Enov8 is pleased to announce its latest environment management ‘innovation’ with the introduction of:
- No Code Lean Synthetics.
A perfect and immediate complement to organizations existing test environment health techniques.
Enov8 ‘no code’ synthetics allows you to automatically, without scripting (or record & playback):
- Determine the health of your test systems using ‘silver thread’ transactions.
- Analyze the underlying component services.
A solution that will allow even ‘mature’ (automated) organizations to find a significant ROI.
ROI of Enov8 “No Code Lean Synthetics” Framework
- Time to build each script originally is 30m (inc analysis, design, build & test).
- Estimated maintenance and execution of script 30m pa.
- Annual cost of Lean Synthetics:
500 x 1-hour x $100 (hourly charge rate) = $50K Year-1 ($25K Y2 onward).
- ROI (compared to Manual health checks) = 2.95M (Year1) and 2.975M (Year2+)
A significant ROI would also be found if we were comparing it to a test automation framework.
- ROI (compared to test automation health checks) = 1.55M (Year1) and 775K (Year2+)
Enov8 Lean Synthetics is now available to Enov8 Environment Manager customers.
Innovate with Enov8
If you are interested in learning more about IT & Test Environment Management and IT Release Management, contact us about EcoSystem.
Ecosystem is a fully configurable and easily integratable solution that comes with out of the box “enterprise management” functions that support IT & Test Environment Management, Release Management, Data Management, IT Operations Management, Configuration Management & Service Management.
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry from Software Engineering, Architecture, IT & Test Environment Management and Executive Leadership. Niall has worked with, and advised, many global organisations covering verticals like Banking, Defence, Telecom and Information Technology Services.
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...
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...
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...
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...
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...
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...