by Angela Guess
Ray Scott of Computerworld UK writes that companies are overlooking the important practice of Test Data Governance. He states, “Try searching some of the most popular career and job sites for Test Data Governance roles; I did and found just 15, none of which were directly associated with my search criteria. Upon closer inspection, these roles only scratched the surface of what is meant by test data governance. Why? It is because test data governance has been traditionally overlooked due to the assumption that test data will somehow appear in development when needed.”
He continues, “As a developer, our seed data has traditionally come from handcrafted master files, locally created transactions or by executing in a localised environment. As testers, data has often been prepared in spreadsheets or included in test case definitions. However, the emergence of additional tasks such as load and stress testing, security and on-demand automation, these methods have become inadequate; the need for data has grown.”
