Introducing Test Datasets & Parameters — Your Fast Track to Data-Driven Testing in TestCollab

When you’re shipping features at sprint speed, test management grinds to a halt if you’re copying the same test case a dozen times just to cover new usernames or environment settings. Today we’re excited to roll out Test Datasets & Parameters, a pair of power-ups that let you keep logic and data separate, slash duplication, and turn any manual or automated script into a true data-driver testing machine.

‍

Why we built it

A login flow that accepts three roles and two password patterns already needs six separate executions. Add language, browser, or region and that number skyrockets. Most teams handle this with extra spreadsheets or cloned cases—until maintenance becomes its own full-time job.

Datasets & Parameters solve the problem by letting you design one canonical test and feed it clean, table-driven test data on demand. No more hard-coded strings, no more version drift.

‍

Key concepts at a glance

‍

Why this matters:

• Design once, reuse everywhere—no copy-paste.
• Track pass/fail per data row for instant insight.
• Update live data without touching the test logic.

‍

Building your first dataset (it’s two clicks)

1. Project → Settings → Test Datasets → “Add Test Dataset.” Give it a clear name like “Login Credentials.”
2. Add Parameters (Username, Password, Role ) and type sample values in the grid.
3. Save—done. The dataset is now ready for every test in the project.

Tip: You can also create a dataset on the fly while editing a test case; just type {{parameter}} in any step and TestCollab spawns the column automatically.

‍

Linking data to a test case

‍

Open (or create) the test and replace hard-coded strings:

‍

Step 1: Enter {{Username}}
Step 2: Enter {{Password}}
Step 3: Verify dashboard for {{Role}}

‍

Below the editor, choose Select to reuse an existing dataset or Use as template to clone and tweak one. Edits you make here sync straight back to the project-level table—no duplicate copies to track.

‍

Running the suite

‍

Add the data-driven case to any Test Plan. At execution time every row in the linked dataset becomes its own iteration; testers see real values substituted inline, can pass/fail each row, attach evidence, and leave comments. Results are stored per iteration, so you know exactly which credential pair or config broke the build.

Historical runs keep their original data even if the dataset later changes, giving you perfect audit trails while still letting current plans pull the latest rows.

‍

A lightning-quick example

‍

‍

One dataset, one login test case. Four iterations automatically appear in your run—zero cloning, zero spreadsheets. Need to add a “viewer” role? Drop a new row into the table and you’re covered next run.

‍

Getting started in under five minutes

1. Upgrade, if needed – Datasets & Parameters are available on Elite and Enterprise plans.
2. Create your first dataset as shown above.
3. Refactor your high-value tests to use {{braces}} instead of hard-coded data.
4. Kick off a fresh Test Plan run and watch the iterations roll in.

Full how-to docs:

• Quick-start overview
• Creating & managing datasets
• Linking datasets to a case
• Running tests with datasets

‍

Ready to try?

Head to any project, click Test Datasets, and start feeding your tests clean, reusable data. Your team—and your future self—will thank you. 🎉

‍