New Release: Test Case Parameters


With our new qTest Manager release, we have upped our test execution game with test case parameters.  This will be a big time-saver, allowing testers to run the same baselined test case with various data inputs at run-time, without having to create duplicate test cases.

New Feature: Test Case Parameters for Test Execution 

qTest Manager’s new parameterization feature allows testers to run the same test case multiple times with different data specified at the test step level. 

This new feature will allow test teams to:

  • Store reusable test data in one centralized location 
  • Import existing parameters and data sets 
  • Share data across qTest projects 

Using Test Case Parameters with qTest Manager 

In this example, we are going to be testing the new fields added to the QASymphony “Contact Us” from.  Below are the eight fields that would require data before a user would be able to click the “Submit” button.  

  • First Name (Text Box)
  • Last Name (Text Box)
  • Email Address (Text Box)
  • Specific Reason for Contact (Drop Down)
  • Phone Number (Text Box)
  • Company (Text Box)
  • Where Are You Located (Drop Down)
  • Comments (Text Box)

We could create eight duplicate test cases with different data for each test case.  However, this work would be inefficient and redundant.  Let’s use the new parameterization feature to show how this will streamline your test planning.

Access qTest Test Case Parameters 

To start creating test case parameters, you need to access the nine-box icon in the top right corner of qTest Manager.  A new window will open where you can begin managing your data parameters and datasets.


Create Test Case Parameters

Parameters can be created manually by clicking on the “+Create” button.  In the example below, I’m creating multiple name types for the First Name (Text Box) element on the “Contact Us” form.

Notice that the variable I will use when I create my test case will be @Contact_FirstName.


To import parameter data, select the import wizard where you can view a sample import file.


Now that we have created eight variables with associated data, we can group them into datasets.

Create Datasets with Parameters 

Datasets are a great way to organize test case parameters into groups of data to use during execution.  

For example, I can take the data parameters specific to the “Contact Us” form and create datasets that match a certain type of test I would like to perform, like positive and negative tests.

This is an example positive dataset since it uses the valid data inputs for each field.


Conversely, here is an example of a negative dataset that uses invalid email addresses and telephone numbers.


Test Execution with Parameters 

Now lets bring it all together by creating a new test case with the variables we just created.  

Create a Test Case with Variables 

By typing “@” in a test step, qTest Manager will suggest variable names as you start typing.  This is extremely helpful once you start managing large sets of variables across projects.  Once your variables steps are complete, click the “Create Test Run” button to start inserting parameters for execution.


Add Data to Variables

After you have selected where your new data driven tests are to be organized in test execution, a new “Create Test Runs” window will appear.  In this window, testers can manually select or auto generate test data for each of the parameter variables used in the test case steps.


Under the “Create Run Data” drop down.  Select the “Manually” option.  This will allow you to assign parameter values to each of the test runs that you will add to the grid below.  Here I have created two test runs and selected data for each test step.



If using datasets, simply select the “Date Set” option from the “Create Test Data” drop down menu to see all available datasets that were created using these parameters.  In the image below, we have selected to use the “Positive_Test_Data_ContactUs” test set.  Click “OK”, and then navigate to Test Execution tab.


Execute Test Runs with Test Pad

After the tests are added in Test Execution, you can select each test run and click the “Run” button to launch the Test Pad.

You will now notice that in the test step grid, the data used in each parameter variable will be displayed in bold with blue highlights.  This allows the tester to quickly see what specific data is needed at the test step.


Notice, qTest Manager will store all the test execution history.  This is extremely important when diagnosing why a test failed or why a defect was logged to development.  Now you can trace test run results directly back to the data used without needing to create duplicate test cases.  This will eliminate some redundant activity and improve the overall testing efficiency.

For more information on test case parameters, visit for a complete walk through and guides.

2 comments on New Release: Test Case Parameters

  1. Avatar Juan Garcia says:

    This is a pretty interesting and cool implementation. Though I have not used it yet and really came across it while looking for something else, this is really neat and much more efficient than 1) having multiple test cases for each of these scenarios, or 2) combining all these scenarios into “one big test” which does not reflect the true test count. I also noticed qTest 8.1 will provide some level of built-in UI driven automation which is also a beast in itself. So, it’s like we’re getting two tools/frameworks bundled into one.

    NOTE: I was looking for a way to “label/flag/categorize” our tests (i.e. Smoke, Regression, Functional, Sanity, etc) so we can store our tests in a repository structure reflecting the product’s “architecture” and label/flag/category the tests so I could later on perform tests’ searches based on “test category/flag/label/etc” when creating corresponding test suites. Is this something we can accomplish in qTest?

  2. Can i just create data parameters for the ONE test. We have test cases that have multiple parameters with multiple results per parameter

Leave a Reply

Your email address will not be published. Required fields are marked *

More Great Content

Get Started with qTest