Qase Docs
Help CenterAPI DocsRoadmapSign up for free
  • General
    • Qase docs
    • Get started with the Qase platform
      • Account settings
      • Projects
      • Test suites
      • Test cases
        • Test Case Parameters
        • Test case review
        • Shared steps
        • Import test cases
        • Export test cases
        • Trash bin
        • Muted Tests
        • System fields
        • Nested steps
        • Test case actions
        • Filters
      • Requirements Traceability Report
      • AI Test Case Generator
    • Execute testing
      • Test plan
      • Test runs
      • Configurations
      • Environments
    • Issues tracking
      • Defects
      • Milestones
      • Requirements
    • Analytics
      • Dashboards
      • Queries (QQL, Qase Query Language)
      • Saved queries
    • Webhooks
      • Test Case
      • Test suite
      • Test plan
      • Shared step
      • Milestone
      • Custom field
      • Test run
      • Defect
      • Test review
  • AIDEN
    • AIDEN - QA Architect
  • Guide: Action editor
  • Administration
    • Workspace management
      • Users
      • Invites
      • Groups
      • Roles
      • Fields
      • Custom fields
      • Notifications
      • Tags
      • Attachments
      • Audit logs
      • Hotkeys
    • SSO / SAML instructions
      • AzureAD
      • OneLogin
      • Google Workspace
      • Okta
      • JumpCloud
    • SCIM
      • User lifecycle management with SCIM
      • Enable SCIM
      • Users
      • Discovery features
      • Errors
    • Security
      • SOC 2 Type II / SOC 3
      • ISO/IEC 27001:2022
      • Penetration testing report
      • Subprocessors
      • Qase IP addresses
    • Billing
      • Billing options
    • Subscriptions
      • Free plan
      • Startup plan
      • Business plan
      • Enterprise plan
  • Apps
    • Issue tracking
      • Jira Cloud
      • Jira Server/Datacenter Plugin installation
      • GitHub
      • Asana
      • Linear
      • Monday
      • ClickUp
      • Trello
      • Azure DevOps
      • GitLab
      • YouTrack
      • Redmine
    • CI/CD
      • Jenkins
      • BitBucket
      • GitHub CI
      • GitLab CI
    • Chats
      • Slack
  • Automation
    • Qase API
    • Reporters
      • JavaScript
        • Playwright
        • Cypress
        • Mocha
        • Newman
        • Jest
        • WebDriverIO
        • CucumberJS
        • TestCafe
      • Python
        • Pytest
        • Robot Framework
        • Behave
        • Tavern
      • Java
        • TestNG
        • JUnit 4
        • JUnit 5
        • Cucumber 3 (jvm)
        • Cucumber 4 (jvm)
        • Cucumber 5 (jvm)
        • Cucumber 6 (jvm)
        • Cucumber 7 (jvm)
      • PHP
        • PHPUnit
        • Codeception
      • Kotlin
        • Kaspresso
    • Qase CLI App
      • XCTest
Powered by GitBook
On this page
  • What are parameters in software testing?
  • How Parameters help?
  • Create a test case with Parameters -
  • Executing a Parameterized test case -
  • How is a Parameter group different from a single parameter?
  • Find your parameter siblings from the Run wizard
  1. General
  2. Get started with the Qase platform
  3. Test cases

Test Case Parameters

PreviousTest casesNextTest case review

Last updated 4 months ago

What are parameters in software testing?

In your testing process, Parameters allow you to capture variables that can be reused across of the same . This eliminates the need to create separate test cases or duplicate steps for different conditions.

How Parameters help?

Consider a scenario where you need to test the sign-in functionality of a web application under various conditions. For each user, you’ll need to test each website twice under different conditions (VPN, WiFi, HTTPS, SSO, Cookies), both enabled and disabled.

Parameter 1

Browser

Chromium

Firefox

Safari

Microsoft Edge

Parameter 2

Website

qase.io

blog.qase.io

help.qase.io

Group 1 is a Secure network; Group 2 is an In-secure network.

is on VPN?

is on WiFi?

is HTTPS?

Using SSO?

Cookies Accepted?

Yes

No

Yes

No

No

No

Yes

No

Yes

No

Create a test case with Parameters -


Go to your repository, to select an existing test case, or create a new one.

When you either create or edit an existing test case, you can scroll down to find the "Parameters" section and simply click on the "+ Add Parameter' button.

Then, proceed to add the following test case steps

  • Check the network condition specified (Secure/ Insecure)

  • Launch the specified browser.

  • Navigate to the specified website.

  • Enter the login credentials for the specified site.

  • Click the "Sign In" button.

Executing a Parameterized test case -


When a test case with Parameters is included in a test run, it generates multiple instances of the test case, each corresponding to a specific combination of parameter values.

For example:

  • Test 1: Browser = Chromium, Website = https://www.qase.io, Secure = VPN = Yes, WiFi = Yes, HTTPS = Yes, SSO = Yes, Cookies = Yes ​

  • Test 2: Browser = Chromium, Website = https://blog.qase.io, Secure = VPN = Yes, WiFi = Yes, HTTPS = Yes, SSO = Yes, Cookies = Yes

(and so on, until all combinations are covered)

  • Test 24: Browser = Microsoft Edge, Website = https://help.qase.io, Insecure = VPN = Yes, WiFi = Yes, HTTPS = Yes, SSO = Yes, Cookies = Yes

With single parameters, the total number of test cases is the product of the number of values for each parameter. For example, with two parameters having 3 and 4 values, you get (3*4) 12 test cases.

Given the network security conditions (Secured and Unsecured), it’s impractical to list each component as a separate parameter. Instead, all components are either enabled in a secured network or disabled in an unsecured network. This is where Parameter Groups become useful.

How is a Parameter group different from a single parameter?

To further streamline the testing process, you can group related parameters into "Parameter Groups." For example:

  • Network security: Is on VPN, Is on WiFi, Is HTTPS, SSO sign-in, Cookies enabled

  • Account status: is Active; has a custom role; is a regular user, is Owner

Parameter Groups are useful when not all combinations of parameters are relevant or meaningful. For instance, with “Account Status” parameter, a combination of “not active” and “not Owner” might not exist in your system or be applicable.

In such cases, Parameter Groups help you focus only on practical and realistic combinations, eliminating unnecessary tests. This ensures that your testing is efficient and covers only meaningful scenarios.

In our example, although we initially had 12 combinations for the single parameters, each of these needs to be tested on both Secure and Insecure network groups. As a result, the total number of test cases in the run will now be 24.

In a test run, the total number of parameter combinations for a case cannot exceed 1,024.

Find your parameter siblings from the Run wizard

In the Test Run dashboard, selecting a parameterized test case will display a ‘siblings’ tab. This tab shows copies of the test case for all other parameter values associated with the selected case.

multiple executions
Parameters explained using a common testing scenario.
Test Case