The Democratisation of (Test) Data
A glance at industry research from recent years shows that test data remains one of the major bottlenecks to fix in DevOps and CI/CD:
Design Complex Systems, Create Visual Models, Collaborate on Requirements, Eradicate Bugs and Deliver Quality!
Product Overview | Solutions |
Success Stories | Integrations |
Book a Demo | Release Notes |
Free Trial | Brochure |
Pricing |
Our innovative solutions help you deliver quality software earlier, and at less cost!
AI Accelerated Quality Scalable AI accelerated test creation for improved quality and faster software delivery.
Test Case Design Generate the smallest set of test cases needed to test complex systems.
Data Subsetting & Cloning Extract the smallest data sets needed for referential integrity and coverage.
API Test Automation Make complex API testing simple, using a visual approach to generate rigorous API tests.
Synthetic Data Generation Generate complete and compliant synthetic data on-demand for every scenario.
Data Allocation Automatically find and make data for every possible test, testing continuously and in parallel.
Requirements Modelling Model complex systems and requirements as complete flowcharts in-sprint.
Data Masking Identify and mask sensitive information across databases and files.
Legacy TDM Replacement Move to a modern test data solution with cutting-edge capabilities.
See how we empower customer success, watch our latest webinars, read our newest eBooks and more.
Events Join the Curiosity team in person or virtually at our upcoming events and conferences.
Blog Discover software quality trends and thought leadership brought to you by the Curiosity team.
Help & Support Find a solution, request expert support and contact Curiosity.
Success Stories Learn how our customers found success with Curiosity's Modeller and Enterprise Test Data.
Documentation Get started with the Curiosity Platform, discover our learning portal and find solutions.
Integrations Explore Modeller's wide range of connections and integrations.
Curiosity are your partners for designing and building complex systems in short sprints!
Meet Our Team Meet our team of world leading experts in software quality and test data.
Our History Explore Curiosity's long history of creating market-defining solutions and success.
Our Mission Discover how we aim to revolutionize the quality and speed of software delivery.
Our Partners Learn about our partners and how we can help you solve your software delivery challenges.
Careers Join our growing team of industry veterans, experts, innovators and specialists.
Press Releases Read the latest Curiosity news and company updates.
Success Stories Learn how our customers found success with Curiosity's Modeller and Enterprise Test Data.
Blog Discover software quality trends and thought leadership brought to you by the Curiosity team.
Contact Us Get in touch with a Curiosity expert or leave us a message.
4 min read
Mantas Dvareckas 31 May 2023 09:30:00 BST
Delays in testing are often due to testers waiting for data. These data provisioning bottlenecks are generally caused in part by an organisation’s lack of understanding regarding their data and how it flows between their systems. In fact, nearly half of all teams reported that they’re unable to manage the size and complexity of their test data sets [1].
Lacking understanding of complex data is a form of technical debt. Fortunately, there are ways to pay it off, in turn improving the delivery of data to your teams.
This blog sets out how organisations can build a successful test data strategy, including a centralized test data capability. This central test data team can then be used to assess technical debt, start paying it back, and avoid data provisioning delays.
This blog is part 3/4 in our series focused on test data strategy success. Check out the other parts here:
Learn how you can transform the relationship that your teams and frameworks share with data by reading our Test Data-as-a-Service solution brief!
When it comes to data, do you know where technical debt exists within your organisation? In software development, technical debt is the implied cost of additional work caused by choosing a quick fix solution now, instead of using a better approach that would take longer but yield better long term results.
Technical debt is often seen in organisations with one or more of the following symptoms:
There are many reasons why these symptoms might emerge:
In many ways, test data delays are an example of interest an organisation must pay for their technical debt.
Often, organisations choose to deal with data-related technical debt in order to align with global data regulations. By contrast, organisations that start to pay down their technical debt as soon as possible see an acceleration in their testing effort, including the ability to source test data. But what can you do to help pay back technical debt when it comes to data capabilities at your organisation?
One key way that your organisation can start paying back technical debt is by carrying out data analysis and profiling. At Curiosity, we provide extensive capabilities in both. Once implemented, you can use comparison capabilities and living models to help you stay on top of your understanding of changing systems and data structures.
These techniques, and those discussed in part two of this series, help keep you efficient well into the future. Learn more by watching the “Organisation Tech Debt” episode of Rich Jordan’s Test Data at The Enterprise series:
Throughout our test data strategy success blog series, we’ve covered a range of principles and test data management aspects to consider when setting up your test data capabilities. However, we’re yet to ask a key question: Who in your organisation should deliver test data? Should you centralise or federate test data responsibilities?
Assembling a test data team and thus centralising your organisation’s test data capability can save time and avoid dev teams waiting around for data requests to be fulfilled. However, in some cases, you may have a simple requirement for test data. In this case, there’s no better reason for a test team to do it themselves, either by creating or self-serving the data they need.
In other, more complex cases, you are going to need a specialist team to create test data. They will also be needed to engage other support functions in your organisation, for example IT security and data compliance.
A major starting point for understanding who should deliver data in your test data strategy is to understand whether your test teams are testing the system where the data is mastered. Or, do they need to consume data from another system?
As much as test teams want to be self-sufficient, they probably don’t know how to effectively source the data they require and therefore end up becoming reliant on another team to provision the data. A better strategy in that circumstance is to work with a centralized test date team, to ensure that the request and provisioning process is as efficient as it can be.
The benefit of a centralised test data team in this scenario is that they are dedicated to fulfilling test data requests. Your dev and test teams will therefore be able to focus on their work instead of waiting for data requests to come in from another team.
There are other benefits to having a centralised capability for test data in your organisation, including the ability to standardize test capabilities and technologies around common data attributes. Review the Data Regulation blog of our test data strategy success series, and think about how a centralised team can help manage PII (Personal Identifiable Information) and SPI (Sensitive Personal Information). Additionally, consider the economies of scale: Does each team need its own data capabilities, or is it more cost and time effective to source that data from a single team?
No matter who manages data at your organisation, it’s important that they are conscious of and facing the questions we’ve discussed in this series of blogs. Additionally, they require the skills necessary to overcome the hurdles that will inevitably come to light when you seek to understand the data in your organisation.
Learn more by watching the “Who Delivers The Data” episode of Test Data at The Enterprise by Rich Jordan:
Working towards reducing technical debt and improving data provisioning at your organisation is key to implementing a successful test data strategy. Consider the questions raised in this blog and the whole blog series so far; being able to address these concerns will help you create an effective test data capability within your organisation.
Here are five key questions that you should be able to answer when it comes to technical debt and data delivery at your organisation:
Knowing the answer to these questions will help you improve your testing and deliver a far more effective test data strategy!
Watch the complete Test Data at The Enterprise series by Rich Jordan to learn how you can introduce six tenants for a better Test Data Strategy at your organisation!
Footnotes:
[1] Sogeti, World Quality Report, 2021-22. Retrieved from: https://www.capgemini.com/insights/research-library/world-quality-report-wqr-2021-22/
A glance at industry research from recent years shows that test data remains one of the major bottlenecks to fix in DevOps and CI/CD:
For many organisations, test data “best practices” start and end with compliance. This reflects a tendency to focus on the problem immediately in...
In 2023, test data remains one of the biggest blockers to fast and effective software delivery. Outdated test data management (TDM) practices don’t...
Today, there is a greater-than-ever need for parallelisation in testing and development. “Agile” and iterative delivery practices hinge on teams...
Today, organisations utilise and adopt a range of technologies, both old and new, in service of enabling their “agile” delivery methodologies. Yet,...
With the rise of agile and DevOps practices, software testing is more important than ever for delivering high quality applications at speed. However,...
It’s 2024 and the risks associated with poor test data practices show no signs of abating.
In 2023, (test) data availability, quality, and compliance risks remain a major headache for software development.
At Curiosity, we talk about test data extensively, because we believe test data is repeatedly neglected in testing and development discussions....