Parameters let you run the same test case with different input data — data-driven testing without duplicating cases.
Overview
A single test case often needs to be executed under multiple conditions: different browsers, different user roles, different environments. Parameters capture those variables directly on the test case.
When the case is added to a test run, Qase automatically generates one case instance for every combination of parameter values, so you write the case once and execute it many times.
Parameters come in two flavors:
Single parameters — independent variables (e.g., Browser, Operating System). Qase generates the full Cartesian product of all single parameter values.
Parameter groups — a set of related variables where each row represents one meaningful combination (e.g., a "Secure network" row where VPN, HTTPS, and SSO are all enabled). Groups avoid generating nonsensical combinations.
Adding parameters to a test case
Open or create a test case in the repository.
Scroll to the Parameters section.
Select + Add Parameter and choose the type:
Single parameter — provide a name and a list of values.
Group parameter — define column headers (variables) and add rows, where each row is one valid combination.
Example: single parameters
Parameter | Values |
Browser | Chromium, Firefox, Safari, Edge |
Website | qase.io, blog.qase.io, help.qase.io |
This produces 4 × 3 = 12 test case instances in the run — one for each browser/website pair.
Example: parameter group
VPN | WiFi | HTTPS | SSO | Cookies |
Yes | No | Yes | No | Yes |
No | Yes | No | Yes | No |
This group produces exactly 2 instances (one per row), not the 32 that five independent binary parameters would generate.
Combining singles and groups
When a test case has both single parameters and a group, the total instances equal:
product of single parameter values × number of group rows
From the examples above: 12 (browsers × websites) × 2 (network conditions) = 24 instances in the run.
Limit: A single test case cannot exceed 1,024 parameter combinations in a run. If your parameters produce more, reduce values or split into separate cases.
Running parameterized test cases
When you start a test run containing a parameterized case, the run wizard expands it into individual instances. Each instance shows its specific parameter values, so testers know exactly which combination they are executing.
Sibling navigation
Inside a test run, selecting any parameterized instance reveals a Siblings tab. This tab lists all other instances of the same test case with their parameter values, making it easy to jump between combinations without scrolling through the full run.
Shared parameters
Shared parameters are defined at the workspace level and can be attached to test cases across multiple projects. They are useful when the same variable set applies broadly — for example, a "Supported Browsers" parameter used by every project in your organization.
Creating shared parameters
Go to Workspace → Shared Parameters.
Create a single or group parameter and define its values.
Select which projects should have access.
Once created, the shared parameter appears alongside local parameters when editing any test case in an enabled project.
Attaching to test cases
In the test case editor, the Parameters section separates options into:
Single Parameters (local)
Group Parameters (local)
Shared Parameters (workspace-level)
Attach a shared parameter like any other — but note that shared parameters cannot be edited from within a test case. To change values, go back to Workspace → Shared Parameters.
Editing and propagation
Changes to a shared parameter apply automatically to every test case that references it. This is the same propagation model as shared steps — update once, apply everywhere.
Deleting shared parameters
When deleting a shared parameter, choose one of two options:
Convert to local — each test case receives its own copy of the parameter values, which can then be edited independently.
Delete from all cases — the parameter and its values are removed everywhere.
Tracking usage
Open any shared parameter and switch to the Usage tab to see:
Which projects have access.
How many test cases reference the parameter.
How many of those cases are currently in review.
FAQ
How does the 1,024-instance limit work with shared parameters?
The limit applies per test case, regardless of whether parameters are local or shared. The total product of all parameter values (single and group combined) must not exceed 1,024.
Can I mix local and shared parameters on the same test case?
Yes. Local singles, local groups, and shared parameters all contribute to the total combination count.