Integrating test data allocation into your automation framework enables you to specify the test data you need for your automated tests. This has two core benefits:
Test data specifications can be defined for a vast array of data sources and can then be easily imported into your automation framework to facilitate the creation and /or resolution of data just-in-time before the automation executes.
The test data can be specified to be allocated only to specific test cases. This avoids the problem of interlock where test cases interfere with other test data being used in other tests. Unique test data allocation ensures a data row is only consumed by the test case it is defined for. This makes automation much more robust as you always have the test data you require available, avoiding brittle tests.
How it Works
Test Data Allocation works in three main phases:
Phase 1 – Firstly, the test data required must be specified and exposed as a test data criterion within the data catalogue (covered in the previous sections).
Phase 2 – Secondly, the automation framework must call the data catalogue API to execute and run the data allocations (this phase finds and makes the right data then assigns it to each test instance).
Phase 3 – Finally, each test can retrieve the allocated data values which can then be used within the automation framework to perform the required actions across user- interfaces, APIs, mainframes, ETL environments, and much more. This is built to plug directly into an automation framework independent of the language or type of automation being executed.