Test Data Management (TDM) - Mapping Test Data

What is TDM Mapping?

When Test Data is needed in order to execute tests across various scenarios, you can use the TDM feature in order to map a Data Source to a particular Test Case. This article will show you how to map data from multiple sources to a single test case  There are two methods to map data to a test case:   

  1. Auto Mapping
  2. Manual Mapping

There are two types of mappings: 

  1. Read
  2. Write

Read mapping reads data from the Data Source for taking data from that source and putting it into the test case. An example might be entering a Username and Password that was previously stored in a .csv file or a database.

Write mapping supports temporarily stored data within a Test Case or Orchestration at the time of execution. The data stored in a Write can be used within the same orchestration or test while that test is running. An example might be having the first test case within an orchestration create an account and store the random credentials that might be used to create that account. If later in that workflow, whether in the same test, or another test within the Orchestration, you can Read from those same columns in order to reuse the random data that was generated with the Write mapping.

NOTE: TDM Data Mapping supports character data to include foreign accent words.


Auto Mapping:

Auto Mapping supports downloading a template for the test case so that, all at once, all mapping may be configured in bulk. Only Actions Input, Verify, PageInit, and Clicks are supported with Auto Mapping. Other Action types must be manually mapped. TDMAuto9.png

  1. Click the TDM button to open the available Data Source list.
  2. Click the Data Source.
  3. The Auto Mapping workflow will open to the Action matching the first column of data. Confirm the match and the Mapping Type, then click Attach.
    NOTE: You may click Attach All to map the data set without viewing each Action.
  4. Continue Attaching Columns to Actions. Click Done.
  5. Review the Mapping. View by Mapped Columns, Missed Columns, and Unified View. Click OK.
    1. Mapped Columns
    2. Missed Columns
    3. Unified View
  6. Each Action mapped to the Data Source will display a label in the Action footer. Click the label to Edit the mapping and click the X to Delete.
  7. In addition, all Data Sources mapped in a Test Case will display on the Test Details page.

Manual Mapping in Test Detail Page

Manual Mapping is available for most Action types and may be mapped to any Attribute for an Action

  1. Select the Action and expand to see Action Details.TDMManual1.png
  2. Click Add Test Data.

  3. Select the Data Source, or create a New Data Source as needed.

  4. Select the Column that you'd like to map to the Action.
    NOTE: If the user maps a column and that value happens to be blank, the attribute mapped will be set to "blank".

  5. Select Mapping Type for a Read or Write mapping.

    1. For Read mapping, select Delete Data Source row. After executing this test in a TDM Orchestration run, the data source row being used will be deleted.
      NOTE: All data sets using that data source row will also be removed. This is great for scenarios where you have one-time-use data.

    2. For Write mapping, select Update Data Source row. After executing this test in a TDM Orchestration, the data source row being used, in addition to the data set, will be updated to match whatever data was written to this column. You also have the option to select Add a new Data Source row. If this is selected a new data source row will be added based on the resulting data set record.

  6. Click Next.

  7. Select the Attribute that you would like to map. The current value of that attribute will be shown under Default Value. If a random value was selected in the test case, you may see something similar to [functionizeappType].
  8. Click OK to save the mapping.
  9. The mapping is now visible in the Action footer. Click the label to Edit the mapping or remove by clicking the X.

Manual Mapping in Slider View

You can also add, edit, and delete mappings while in Slider View the same as on the Test Detail page.

  1. Click the Gear icon on the Action to open Action Settings.
  2. Click Add Test Data.
  3. Select the Column, Mapping Type, and Data Source Row instructions as above. Click Next.
  4. Set the Attribute for the Action and click OK.

Create a Data Source within a Test Case

  1. Open a test in your Project.

  2. Click the TDM button.

  3. Click Add a Data Source.
  4. In the Create Data Source modal, give the new source a meaningful name and select the file type.
  5. Upload your file. Click Submit. See below for instructions on Creating a Data Source for Auto Mapping.
  6. Your new Data Source will be in the list for selection.

Create a Data Source for Auto Mapping

Functionize offers you a template to create data sources specifically for Auto Mapping your data to your specific test. 

Click the TDM Sample download button.

Two options will populate on the dropdown selection:

  1. Download Template
  2. Download Selected Template 
    • A Download Selected label will appear along with check boxes to select the actions for the template. This option is used for customizable selections, meaning there are specific steps to be parameterized - not every single step of the test.
    • Select All customizable Actions with the top check box, select by Instruction, or select Actions individually.
    • Cancel by clicking the X in the label.

Once an option is selected, a .csv file named TestDataSource containing all (or selected test information) will download. The columns will correspond to the Actions in the test to be mapped. Do not change the column names or the Source will not Auto Map.


Add data as needed in the provided columns.
NOTE: If a column has a blank value, the attribute mapped will be set to "blank". Some examples would be adding multiple URLs, emails, or names (or whatever the data may be for a particular test case). Mapping a column is optional and can be skipped entirely. 

When all data is entered in the file, save it. Remember to save the file in one of the accepted formats: CSV, Excel, DB, or JSON. The name of the file itself will not affect Mapping.