---
title: "Parameters & Values"
canonical: "https://docs.getxray.app/space/XRAYCLOUD/44565547/Parameters%20%26%20Values"
format: markdown
---
Table of Contents
> Macro (toc)
# Introduction
**Parameters** are the factors being tested in Test Case Designer [Scenarios](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565557), such as **Browser Type**, **Payment Method**, or **Age**.
When [creating your Test Model](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44566012), you must define which parameters to include and what their values are.
**Parameter values** represent the different ways a parameter can vary. These are the specific values selected for a given parameter in a Test case. For example, parameter values for **Browser Type** might include **Google Chrome**, **IE**, or **Safari**.
Deciding what to include as parameters and values is crucial, as it directly impacts Test Interaction Coverage and efficiency. Missing key parameters can result in Testing gaps, while including unnecessary ones can lead to redundant Tests, wasting time and resources.
# Operations
## Creating a Parameter
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ✅ **Description vs Numbers**
> > ✅
> > ✅ In some situations, descriptive fields are not the best/most practical way to use parameters in your Test Model.
> > ✅
> > ✅ In the example (Figure 4), you can see the parameter *Age* with a descriptive value (Figure 4 - 1).
> > ✅
> > ✅ 
> > ✅
> > ✅
> > ✅ Instead of descriptions, maybe you could use the numbers for the ones you want tested. In the example (Figure 5), you can see the same parameter *Age* but now with a numerical value (Figure 5 - 1).
> > ✅
> > ✅ 
### Creating a Parameter with a Ranged Value - Boundary Testing
Instead of using descriptive or numerical values, you can use **range values**.
Range values are helpful when testing around specific cutoffs for business rules, where adding too many individual values to your parameters would be inefficient.
To create a range value, use the format `number space hyphen space number` (i.e., `# – #`). Xray Test Case Designer will recognize this as a range of values from which to select.
See the example with the Parameter *Age* in Figures 6 and 7.
Additionally, a range value is treated as a set of numbers that includes the endpoints. Xray Test Case Designer will prioritize the boundaries of the range but will also randomly select numbers from within it as needed for the Tests.
See below (Figure 8) how the range values are converted into values for use in your Tests.
Xray Test Case Designer can recognize many options for ranges. We recommend having the same number of decimals across all numbers in a range. Additionally, all ranged values **must not** **overlap **(you can have gaps though, e.g. 1-10, 15-21). The tool will not recognize logic like in alphanumeric codes either.
See below (Figures 9 and 10) examples of ranges as inputs followed by the outputs provided.
## Creating a New Value Expansion
If your model includes a long list of values, you risk generating more Tests than necessary. The **Value Expansions** feature can significantly reduce the number of Tests by maximizing variation without impacting the test suite size. For example, using this approach instead of 45 individual values results in 144 fewer Tests. It is the primary way of implementing equivalence classes for non-numeric parameters in Test Case Designer.
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ℹ️ - If you would like each of these five sub-values to appear in your [Test scripts](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44565563) with equal weighting (e.g., having *Porsche* appearing in approximately as many Test cases as *Ferrari*), the *Use evenly* option (Figure 13 - 3) is already set by default.
> > ℹ️ - If you would rather have the sub-values that you put towards the top of your list appear more frequently, select the *Bias initial value(s)* option (Figure 13 - 2).
> ⚠️ **A Caveat on Value Expansions**
> ⚠️
> ⚠️ Expansions are an excellent way to introduce more variation in your Tests without increasing the number of Tests. However, it's important to note that not all value expansions are **guaranteed** to be included.
> ⚠️
> ⚠️ For example, if you have 10 value expansions for a parameter in a Test Model that generates 20 Tests, that parameter may only appear in a few of those Tests - perhaps five. As a result, only half of the value expansions will be covered.
## Viewing Parameters
### Standard View
Standard is the default view (Figure 12 - 3), where you have visual access to all the available parameters and all the main actions you can perform on them.
### Bulk View
Bulk view (Figure 14) enables (Figure 12 - 4 to access it) you to view and edit your parameters faster and displays parameters and values in a plain text style (Figure 14).
> ℹ️ Changing the name of a parameter or value in **Bulk Edit** mode causes Xray Test Case Designer to treat the edited parameter or value as a new entry. This triggers a warning message about the potential loss of associated constraints, requirements, or value expansions.
> ℹ️
> ℹ️ Typing new parameter names in **Bulk Edit** does not provide access to the auto-suggested list of existing reusable parameters, which is available when adding parameters to standard **Edit** mode. Additionally, you cannot create value expansions from the **Bulk Edit** screen (Figure 14).
## Editing/Deleting a Single Parameter & Value
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
## Reordering a Parameter
> Macro (ui-steps)
>
> > Macro (legacy-content)
>
> > Macro (legacy-content)
>
> > ℹ️ You can also use the Bulk option (Figure 19 - 4) to re-order your parameters.
Support/Troubleshooting
If you have questions or technical issues, please [contact the Support team via the Customer Portal (Jira service management)](https://jira.getxray.app/servicedesk/customer/portal/2/user/login?destination=portal%2F2%2Fcreate%2F28) or [send us a message using the in-app chat](https://getxraydocs.atlassian.net/wiki/spaces/XRAYCLOUD/pages/44577312).