Data Find and Reserve
    • Dark

    Data Find and Reserve

    • Dark

    Article Summary

    Search for data using an easy-to-use form. Optionally reserve the data so that others don't use it. If no data is found, then make any missing data.

    The outcome of a Data Find & Reserve activity is to execute a ‘Data Request’ which generates a Find Submit Form for an end user. A 'Data Request' Data Find & Reserve can use data across schemas and databases. 

    This page shows the Test Automation Data Activity for Data Find & Reserve. Optionally reserve the data so that others don't use it. If no data is found, then make any missing data.


    Data Requests - How To

    Check out our Test Data Automation 101 documentation on using data files to learn more.

    3 pre-requisite Objects are required when configuring the Data Find & Reserve, of which the first two help initialise the final Object. They are all created using Test Modeller. Here you’ll see how to use them for configuring a Data Find & Reserve, Data Activity, with the purpose of generating a user-friendly Find Submit Form.

    These 3 Objects get listed in the spanning Components panel of the Data Activity window alongside the outcome of a Find Submit Form:

    • Definition (brought into the Data Activity window)
    • Test Criteria (created in the Data Activity window) producing a Ruleset
    • Allocation Pool (initialised in the Data Activity window) producing a Starter Allocation List

    Set Up

    Definition (of the Data Source) – Object One

    This can be a query against a view

    • in a database
    • from a file

    Purpose: It’s for making views of the columns that will be available for reserving as you configure the Data Request. Once created in Test Modeller, go to: TDM > Data Dictionary > Click a Definition, and you'll see the views. In the views, click to see the columns that are available for reserving the Data Request.

    Test Criteria – Object Two

    This is accessed through TDM > Data Catalogue > Catalogues > Test Criteria. From there you'll see Inputs and Outputs. In this example:

    • Input is set up as a generic Where clause, dynamic be replaced on Execution
    • Output is set up as the IDs that you want to be used/found

    Allocation Pool – Object Three

    This needs to be Initialised for later use. An Allocation Pool records executions of Criteria and manages Execution Results of reservations. To initialise it you must define an Allocated Test. In the pop up > choose the Test Criteria and put in a Value for the Where clause (because it’s not yet dynamic). In the example we want to Find & Reserve card_brand = 'Visa'.

    After the Allocation Pool is initialised, Results will show ie, ‘Found x Rows’

     Note: An Allocation Pool can manage one or more Starter Allocation Lists.


    Start creating the Data Find & Reserve, Data Activity!

    To start making a new activity: In the left menu in Test Modeller go to Explorer > (in the Models window: top, right blue button) click +New Item > choose Data Activity.

    What’s on the screen? You’ll see it’s divided into Components (where you’ll see each component appear and can be actioned once it’s been added), an editable Properties Configuration panel, and below which is Add Components (blue) and Actions (green).

    Attach the view – Component (Object 1): Select the Scanned Table. Add Definition, Schema and Table.

    A note about adding Tags and Descriptions:

    • Descriptions: these are generally more user friendly wordings which appear in the Find Submit Form that you’ll generate
    • Tags: for grouping different Input attributes in order to use drop downs, pick lists, etc

    Create a select Ruleset (ie, the columns which will be presented as Input for Criteria in the query). So, in the spanned Components panel click the blue Execute button.

    Edit the incoming Column selection listed in the spanning Components panel. Decide which attributes of the Data Request to keep Active or make Inactive according to the user needs and what appears on the generated form. To do so, click the Ruleset by name.

    Create the specific Starter Allocation List (a list which is specific to this momentary task). So, in the Actions panel click Create Starter List. See it appears listed in the spanning Components panel. Click its name to initialise it.

    If a placeholder base list appears, remove it.

    Outcomes you should see listed in the spanning Components panel:

    • Definition(brough into the activity)
    • Ruleset(created in the activity)
    • Starter Allocation List(initialised in the activity)

    Continue the configuration with the Objects created beforehand, before having started the Data Activity before going onto Generate the Find Submit Form.

    To do so, click the Edit button in the spanning Configuration panel. Choose the Lookup Type, Test Criteria, Starter Allocation List (ID) and Allocation Pool (ID).

    Generate or create the Find Submit Form

    To do so, in the bottom Actions panel, click Create Find Submit Form. Complete the parameters.

    Tags: this is where you can select tags to group attributes

    Added outcome to the previous outcomes list in the spanning Components panel is:

    Find Submit Form (with parameters)

    Click Execute again to add and modify parameters. Also add a Use Case Name and click the Unique Lock option to Reserve the data.

    To view the Results do this by downloading either the Excel sheet or through viewing the Results in the Job Queue in Test Modeller window. Alternatively to see the actual contents of the Find & Reserve in columns and rows head to the Reservation Lists via the left panel menu, click it and then click your named Data Reservation List.

    Forms Editor

    After having executed a basic Find Submit Form you can continue to edit it. To do so, in the spanning Components panel under Actions click Modify (on the listed Find Submit Form). Then in the form editor choose from:

    • pick lists
    • checkboxes
    • test boxes
    • values
    • etc

    You can also move and reorder how the fields appear on the final Find Submit Form.

    General info on running Jobs for Data Activities

    A database activity is created by adding components into the activity including and not exclusively: a Definition version, Submit form, and - specifically for a Data Find & Reserve, Data Activity - an existing Starter Allocation List. Also see the available specific Actions, including but not exclusively, for a user to - specifically for a Data Find & Reserve, Data Activity - to generate a form to Snapshot a database. 

    Note: A Data Activity job can be executed from within the Data Activity space or from the VIP Executor (where a user normally requests jobs). The user then sees a spreadsheet to show the differences in rows of inserted or edited data before and after a test has finished.