For many large enterprises, the mainframe and z/OS platform have been the backbone of business-critical applications for decades. Huge volumes of data still reside in Db2, VSAM, or IMS – a result of years of continuous operation. The corresponding applications are often written in Cobol, but the internal expertise to
Example of a typical scenario prior to the implementation of an automated TDM solution. It illustrates a real-life example of a large insurer, was able to master all its challenges by using the test data management software “XDM” from UBS Hainer
The TOP5 ARGUMENTS why developing your own test data management solution is no longer profitable today. TDM has become a complex issue. For this reason, there are experts today who offer mature TDM solutions to the market
In the process of software development, tests need to be performed repeatedly. Depending on the stage of development, various test data, from individual test case data to bulk data, is required. There are three basic options for obtaining this test data: The manual creation of test data, the creation of synthetic test data and the conversion of productive data into test data
Best-Practice: Test data procurement in the context of continuous software development (PART 3/3). Before the new or modified applications go live, system, release, load or performance tests are applied. For this purpose, no fine-grained customized test case data is needed, but production-related data in larger quantities is required. These tests are
Best-Practice: Test data procurement in the context of continuous software development (PART 2/3). The further development of an application usually means that different features or even bug fixes need to be implemented. Ideally, each feature gets its own environment. This environment contains only the relevant data for that particular case.
Best-Practice: Test data procurement in the context of continuous software development (PART 1/3) Due to the massive increase in data-driven business models (from data-enhanced to
