• Using VIP to Make Data if no Data is Found

  • Exposing Test Types into Modeller

  • Adding Test Data Finds and Makes to Modeller


Using VIP to Make Data if no Data is Found

If your Test Type does not find any data with the combination of parameters that Modeller has provide you can make a call to make any missing data. This feature allows you to stabilize frameworks and ensure that all the automation runs cleanly.

You can invoke any process you like to create the data, if you already have a Selenium script to create data then invoke it from a VIP flow and pass down the parameters.

To set this feature up create a VIP flow that will make the missing data and add it as a process to Modeller. Then, add this process into the Test Type definition:

There are a number of steps you need to go through to set this feature up:

  1. Create a flow to call the process or to directly make the data. For example, you could use the VIP TDM feature to create data directly into a database.

  2. Make sure that the parameters that you use to find the data are available in this flow. In other words, the Data lookup will be searching for values based on a list of variables, this same list is going to be used to create the data.

  3. Add the VIP flow as a process in Test Modeller.

  4. Ensure that the ORDER of the input parameters is the same, the names do not need to the match.

The VIP flows has three required parameters, par1, par2 and par3, shown below:

These are mapped in order, here, you can drag and drop to alter the order:

These will be listed in the same order as the parameters in the original lookup:

When you run a find, look at the log results to see if and when data has been made:

Once this has been run, you can check to see if the parameters match and check the make results.


Exposing Test Types into Modeller

Once you have tested that the Test Type is working correctly you can start linking these data searches and makes directly into Test Modeller. You can then run the allocation process just before your automation runs to Find, Make and Allocate the correct data to each Automated Test.

Navigate to the Test Types, in the list of Test Types you will see a column called ‘Expose Module’:

This feature determines if the Test Type is available for the modelling engine to attach to the models. If this is turned off the test type will not be available. You may keep this turned off if you are not using Test Modeller for certain projects or are just using that test type for manual testing.

N.B: If you change any of the parameters, it is worth unchecking and rechecking this button as it will ensure the change is propagated.

Understanding the Parameters

When you build a model, you are defining the different journeys through the application, these could be to drive a UI using Selenium, inject data into an API, or create combinations of data to drive data into a system (data testing).

The Test Cases are in effect different combinations of data, for the test to run we need to lookup data to drive the application correctly. This might be, for example “Use a manager who is not on holiday to approve the request” or “I need a unique employee associated with each test so I can track back when there are failures”. An example of a model within Test Modeller which produces many Test Cases providing full coverage is shown below:

You can set up the data variables in the Test Modeller and then assign them as part of the logic:

These “inputs” are then ready for the Test Data assignment as parameters.


Adding Test Data Finds and Makes to Modeller

To define what test data is required to be used by a model you need to attach waypoints into your model, the Test Modeller pallet is shown below:

There are two ways to do this, Manually and Automatically:

Manually

You can drag a waypoint from the pallet onto the model, as shown below:

Click on the waypoint, in the example above it is ‘Find Campaign’, and go to the Test Automation Tab, then click on actions and add some external automation:

To begin with, set the object module. Click on the drop down and select the ‘Core Test Data Catalogue’ with the data lookups:

Then, for the function, pick the test data type you need and click ‘Save’. You will now be prompted to map the Data Variables in the model:

Inputs are values that you will use to lookup the data with that criteria. Outputs are the returned values from the criteria.

So for example, I need an Opportunity ID which has the Type, Stage and Source set:

These input variables are defined by the model. If the input and output variables do not exist you must define them using the data tab.

Automatically

To save time, you can automatically import a test data type from the Test Automation tab, click on ‘Modules’ and choose ‘Data Catalogues’. Here, select your Test Data Type and import it to the model:

A waypoint will be automatically added to your model. In addition, Data Variables and a block per variable will automatically be created for you, this is shown below:

The Parameters to the Data lookup are set automatically:

This is a much faster and more efficient way to set up ‘Find and Make’ Test Types in Test Modeller.

TEST DATA AUTOMATION TEST DATA ALLOCATION FIND AND MAKES