4. Data Builder

Accurate test data is required to thoroughly test changed code and application functionality. The best test data comes from the live production environment. However, it is not always possible to test applications on massive databases due to runtime, processing power and memory constraints.

Data Builder automates the process of deriving a minimum set of test data from a large amount of live data. It uses the latest Application Program Interfaces available to find the links between files and fields. The extraction process allows data to be copied incrementally, so you can add new conditions to your test databases without regenerating the entire set.

Creating Test Applications and Build Cases: An Application is the top-level container within Data Builder and a Build Case is a set of extraction rules for files in one or more libraries. The Build Case supports files that have triggers, members, constraints and related fields that do not match across files.

Editing the Build Case: Once the Build Case is known to Data Builder, it can be edited. All the physical files are displayed. You identify the first file in the extraction process and enter the selection criteria. To apply the selection criteria to all related files, simply use the Auto Link Dependent option. This option analyses the fields in the selected file and automatically links the fields with the selection criteria to all the related files. Done manually, this can be a time consuming job, but Data Builder can accomplish it within seconds; you can add additional levels of dependent files and selection criteria as required.

Execute Data Builder: When you run a Build Case, you specify the target libraries and if the files should be recreated, the data copy option (add or replace) and if the job should be run in batch.

Progress Reporting: During the extraction job, on-line metrics information is available to advise on the build stage being processed, the file being copied and the estimated extraction time remaining.

Warping a Build Case: After a build case has been executed sensitive data might need to be protected before the database can be used or date related fields might need to be advanced to keep the database current.

Data Builder Application Program Interfaces (APIs): SmartTest400’s open design means Data Builder commands can be used within other SmartTest400 modules and PDM.

To view the full SmartTest400 brochure in PDF format please click here.

For a live demonstration via the web please contact sales@thenon.com or phone +44 (0)20 8607 9336

All trademarks are the property of the respective owners. All rights acknowledged.