Parameters are available in supported rich-text editors and testing workflows. They help teams reuse values without hardcoding the same text in many places.
In supported editors, use one of these options:
$ to open the parameter picker.The parameter picker lets you search available parameters by name or value, then insert the selected parameter into the content.
Parameters can be used while creating or editing repository test cases. They are useful in:
When test content is reused later, the parameter reference keeps the value easier to maintain.
Shared steps can include parameters in step descriptions and expected results. This is useful for reusable procedures that need environment-specific values, URLs, or account names.
When a shared step is reused by test cases, the parameterized content stays consistent with the shared step.
Requirements support parameters in rich-text content. Use them for repeated product names, environment values, tenant names, or other values that may change while the requirement remains the same.
Defects can use parameters in supported rich-text fields, including descriptions and details. This helps teams reference reusable values without typing them into every defect report.
During test execution and test run work, Hawzu can show parameterized test content from the linked test cases and steps. Supported editors in the running-test experience can receive available parameters for review or updates.
The Parameters page tracks usage counts for:
Open a parameter details view to review usage lists and open related items.
Parameters are not meant to replace every repeated word. Use them for values that are reused, likely to change, or easier to govern centrally.
Regular parameters are visible to users with access to the Parameters page, so avoid storing sensitive secrets in them.