Environments
Environments store reusable parameters that are injected into test cases at runtime. Use them to run the same test cases against different configurations - staging, production, or any custom setup - without modifying the test cases themselves.
Environments list
Click Environments in the left sidebar to see all environments.
Name - The environment name. Click to open.
Updated By - Who last edited it.
Updated Date - When it was last changed.
Actions - Delete the environment.
How to create an Environment
-
Go to Environments
Go to Environments in the sidebar.
-
Create
Click + Create Environment in the top right.
-
Name the environment
Enter a name - for example
stagingorproduction. -
Save
Click Save.
How to delete an Environment
Click the red trash icon in the Actions column and confirm deletion.
Parameters
When you open an environment, the Parameters tab is shown by default. Parameters are key-value pairs that QAlity substitutes into test cases at runtime when an environment is selected for a run.
Parameter Name - The key referenced in test cases.
Parameter Value - The value substituted at runtime.
If a parameter has no value it shows as -. Always set a value before running test cases with this environment.
How to add a Parameter
-
Open an environment
Open an environment from the list.
-
Parameters tab
Stay on the Parameters tab.
-
Add
Click + Add.
-
Enter values
Enter the Parameter Name and Parameter Value.
-
Save
Save.
Using Parameters in test cases
Reference any parameter inside a test case using:
{{parameter_name}}
QAlity automatically substitutes the actual value when the test case runs with an environment selected.
Use parameters for values that change between environments - base URLs, credentials, API endpoints, or config keys.
Running test cases with an Environment
Environments are selected at runtime from the run configuration screen when starting a test suite or test plan. QAlity injects all parameter values into the test cases for that run.
Environments are created manually - they are not created by the recorder.
Best practices
- Name environments clearly -
staging,production,regression - Use parameters for every value that differs between environments
- Always set values for all parameters before running
- Delete unused environments to keep the list clean