Datasets, placeholders, and table-driven runs
Tags: dataset, datatable, csv, json, parameters
What it is
Datasets enable table-driven execution by binding CSV/JSON data to placeholders in suite.yaml.
Why it’s needed
- You need coverage across multiple users/roles/inputs without duplicating suites.
- Regulated teams often need repeatable, data-based scenarios.
- Separating logic (suite) from data (dataset) improves maintainability.
Benefits
- More coverage with fewer suites.
- Easier updates when test data changes.
- Supports dev testing and QA regression with the same suite definitions.
How to use it in WebSureQTool
1) Create a dataset (CSV or JSON) with named columns/fields.
2) Reference placeholders in your suite, e.g., ${USER}, ${PASSWORD}, ${BASE_URL}.
3) Bind the dataset to the suite run.
4) Execute as a table-driven run to iterate over rows/records.