Parameters are a powerful abstraction in Hawzu. When used correctly, they make test cases reusable, maintainable, and environment-agnostic. When misused, they can quickly become a source of confusion and hidden coupling.
This guide outlines recommended best practices for defining, naming, using, and maintaining parameters across your workspace and projects.
Use workspace parameters for values that are:
Examples
base_urlapi_keydefault_timeoutsupport_emailWhy
Avoid creating duplicate project parameters for the same global concept.
Use project parameters when the value:
Examples
checkout_flow_versionmobile_app_buildproject_feature_toggleThis keeps projects flexible without polluting the global parameter namespace.
Good naming prevents accidental misuse.
Recommended conventions
login_urlBad
urlvalue1test_paramGood
application_login_urlmax_retry_countpayment_gateway_endpointOnce parameters are widely used, renaming becomes expensive.
Every parameter should explain:
Example
Base URL for the customer-facing web application. Used in login and checkout flows.
Descriptions are especially critical when parameters are used inside rich text editors where the value itself is hidden.
Parameters can be inserted using:
Best practices when using parameters in steps:
Good
Navigate to $application_login_url and verify the login page loads.Avoid
Open $url and do $thing.Not everything needs to be a parameter.
Avoid parameters for:
Overusing parameters can make test steps harder to understand and debug.
Changing a parameter value impacts all usages immediately.
Before updating:
For risky changes, consider:
When deleting a parameter that is in use, Hawzu provides three options:
Best for refactors and migrations. Safely preserves structure.
Useful when parameterization is no longer needed.
Destructive. Removes the variable reference entirely. Use only when you fully understand the impact.
Best Practice Always prefer replacement over removal when possible.
Over time, unused parameters accumulate.
Periodically:
A clean parameter set improves onboarding and reduces mistakes.
Think of parameters as infrastructure, not convenience variables.
Teams that treat parameters seriously end up with:
Parameters are one of Hawzu’s most powerful features when used correctly. A small amount of discipline upfront pays off massively as your test suite and team grow.
If in doubt: