TEST AUTHORING
...
Interactive Test Authoring
Tasks
Parameters in Tasks
2min
It's common to have parameters within tasks, as users often need to run tests with varying values to cover different scenarios. In AI Test Automation, you can set runtime overrides when running a test in standalone mode through the run modal. However, manual overrides arenโt available when running multiple tests, or test suites, via CI/CD integration. To address this, AI Test Automation allows users to set parameter overrides at four levels in a hierarchical structure:
- Tasks: Each parameter has a default value, typically set when the task is created. If no other overrides are applied, this default value is used in any test that includes the task.
- Environment: This override lets you specify a unique value for a parameter when a task runs in a specific environment. For example, if you set an override for Environment 1 but not for Environment 2, the task will use the override in Environment 1 and the default in Environment 2.
- Test: A test-level override supersedes the environment and task-level values. You can also define a parameter override for a specific combination of environment and test.
- Test Suites: This is the highest level in the hierarchy. Parameter overrides set at the test suite level apply during test suite execution and take precedence over all other levels.
Here is a short video explaining how to set overrides for a Task parameter.
To set the task level default simply edit the value on the parameters modal as shown below.
๏ปฟ
๏ปฟ
๏ปฟ
