Search

Mapping Test Data

When test data is needed to drive test execution across multiple scenarios, you can use the Functionize TDM (Test Data Management) feature to map a Data Source to a particular test case. This guide explains what test data mapping is, how it works, and how to configure mappings using Auto Mapping or Manual Mapping.

What is Test Data Mapping?

Test Data Mapping connects a Data Source to a test case, allowing for data-driven testing. Instead of hardcoding values, you can parameterize test actions so they draw data dynamically from files, databases, or Google Sheets.

There are two mapping methods and two mapping types:

Mapping Methods

  • Auto Mapping → Bulk-configure mappings using a downloadable template. Best for setting up multiple mappings at once.
  • Manual Mapping → Configure mappings for individual actions, giving you full control and flexibility.

Mapping Types

  • Read Mapping
    • Pulls data from a Data Source to use in the test.
    • Example: entering usernames and passwords from a CSV file.
    • Option: Delete Data Source Row → removes a row after execution, making it ideal for one-time-use data (e.g., unique credentials).
    • Note: Deleting a row also removes it for all test cases using that data source.
  • Write Mapping
    • Saves data generated during execution back into the Data Source.
    • Example: creating an account and writing the generated credentials for reuse in the same or another test.
    • Options:
      • Update Data Source Row → overwrite an existing row.
      • Add New Data Source Row → append a new row.
    • Note: TDM mapping supports character data, including non-English and accented characters.

Auto Mapping

Auto Mapping simplifies setup by letting you download a template of supported test actions and configure mappings in bulk.

Supported Action Types

  • Input → Enter values into fields.
  • Verify → Check actual vs. expected results.
  • PageInit → Initialize a page before test actions.
  • Click → Interact with buttons, links, or elements.
  • Select → Perform a selection from a dropdown.

Other action types must be mapped manually.

Steps to Auto-Map a Data Source to a Test Case

  1. Open Data Source List
    • Click the TDM button to view available Data Sources.
  2. Select a Data Source
    • Choose the Data Source you want to map. Use the search capability if needed.
  3. Open Auto Mapping Workflow
    • The workflow aligns test actions with Data Source columns.
    • Confirm column matches, select the Mapping Type, then click Attach.
    • To skip confirmation, click Attach All.
  4. Complete Mapping
    • Map all selected actions and click OK.
  5. Review Mapping
    • Use one of the available views:
      • Mapped Columns → shows mapped actions.
      • Missed Columns → shows unmapped actions.
      • Unified View → shows both.
  6. Edit Mapping (Optional)
    • Each mapped action displays a label in the footer.
    • Click the label to edit or x to remove it.
    • If desired, check the following boxes:
      • Ignore Blank Columns → Check this box to ignore blank columns from the dataset.
      • Delete Data Source Row → Check this box to delete the row of data after use. This is ideal for one-time use credentials.
  7. View Mappings
    • All Data Sources mapped to the test case appear on the Test Details page.

Manual Mapping

Manual Mapping provides fine-grained control, letting you link any attribute of an action to test data.

Manual Mapping from the Test Detail Page

  1. Select Action → Expand the action in Test Details.
  2. Add Test Data → Click Add Test Data.
  3. Select Data Source → Choose an existing Data Source or create a new one.
  4. Select Column → Choose the column to map, then click Next.
    • If blank, the mapped attribute will be set to “blank.”
  5. Select Mapping Type → Read or Write.
  6. Set Attribute → Pick the attribute to map (default values are shown).
  7. Save Mapping → Click OK.
  8. Edit Mapping → Mappings appear in the action footer; click to edit or x to remove.

Manual Mapping in Slider View

You can also manage mappings directly in Slider View:

  1. Open Action Settings → Click the gear icon on the action.
  2. Add Test Data → Click Add Test Data.
  3. Select Data Source → Choose or create one.
  4. Select Column & Mapping Type → Configure Read/Write and row handling.
  5. Set Attribute → Define which attribute to map.
  6. Save → Click OK.

Best Practices

  • Use Read Mapping with Delete Row for one-time-use test data (e.g., unique email addresses).
  • Use Write Mapping for dynamic workflows (e.g., account creation where generated credentials must be reused).
  • Always review mappings in Unified View to ensure full coverage.
  • Name Data Sources and columns clearly for maintainability.

By using Test Data Mapping effectively, you can unlock powerful, data-driven testing in Functionize—making your test cases more flexible, reusable, and reflective of real-world scenarios.