LF

Holistic Test Data Management – Beyond ETL

01

MAY, 2018

by Niall Crawford

So, you’ve got a team responsible for Test Data Management.

Your project puts in a request, they grab copies from production, mask them, subset them and deploy them into your Test Environments. Easy Peasy! … Well probably not, probably a lot of paperwork, engineering & provisioning effort. And then the issues really start.

  • The data lacks end-to-end integrity i.e. the data is broken.
  • The developers & testers can’t easily find the data they are looking for.
  • And when the IT teams do find the correct data-points they can use, they all use it.

Causing contention & data related test defects. And it all starts to grind to halt, suddenly Development & Test cycles are being blown out.` And then to add insult to injury, an honest Test Analyst, notices that not all the data has been masked. A serious concern when one considers that’s where your project teams spend 95% of their time, and the opportunity for information to be misplaced or stolen is high. A suboptimal situation, which exposes the customer to:

  • Identity Theft & Fraud

And exposes your own organisation to

  • Compliance Penalties
  • Industry sanctions
  • Brand Damage
  • Consequent Lawsuits

Not exactly ideal, particularly with data compliance legislation like GDPR that will sting you for 4% of turn-over. Yet I can virtually guarantee, sadly, that the above scenarios describe most organizations today. The reason why data is such a problem – is sixfold:

  1. Enterprise architectures are typically diverse & distributed.
  2. Environment & data footprints are under constant change.
  3. Individual databases are often large, poorly defined or understood.
  4. System & data documentation often suffers from technical debt.
  5. Easy to make mistakes during data Subsetting (causing integrity health issues).
  6. Very easy to make mistakes during data obfuscation exercises (causing PII leakage).

The traditional ETL approach to Test Data Management simply isn’t good enough.

  • It is too Slow
  • It is too Manual
  • It is too Error-Prone &
  • It is not customer / user-centric

There is a fundamental need to recognise that successful Test Data Management can’t rely on ETL alone. Instead, organizations must start looking at data a little more broadly and leverage more automation to ensure accuracy, quality, compliance & ease of end-user consumption.

Enter the Holistic Test Data Management (HTDM) Framework

Designed by Enov8, the HTDM Framework is used to contextualise the broader aspects of Test Data Management. A set of “Lego” blocks that call out the broader considerations and needs of an automated test data solution. Build around the traditional ETL, the HTDM promotes supporting capabilities like: Data Requirements Capture – So you have a clear understanding of consumers (testers & projects) needs. Automated Data Profiling – To rapidly understand data structures and PII risks (pre-ETL). Automated Data Validation – To rapidly determine if created data (post-ETL) is free of production patterns and healthy (has integrity). Test Data Mining – So Testers can visualise, understand and find end-to-end (cross-system) data without building complex queries and scripts. Test Data Bookings – So test data can be assigned to test cases or teams and avoid the risk of overwrite.

Key Benefits of creating an HTDM Framework

  • Understand your Data
  • Improve Compliance.
  • Ensure Data Health
  • Ease of Consumption (based on your needs, healthy & easy to find)

All of which leads to happy testers and streamlined project delivery.

Learn More or Share Ideas

If you’d like to learn more about Data, Release or Environment Management or perhaps just share your own ideas then feel free to contact the enov8 team. Enov8 provides a complete platform for addressing organisations “DevOps at Scale” requirements. Providing advanced “out of the box” Holistic Test Data ManagementIT & Test Environment ManagementRelease Management capabilities.

Niall Crawford

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.

Relevant Articles

Data Security (Scale and Bees)

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

The Test Environment Management Plan Template

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

Five Reasons You Need Enterprise Configuration Management

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

Software Testing Anti Patterns

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

A Brief History of Configuration Management

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

5 Red Flags DevOps Is Failing

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