Parameter Overriding

What is parameter overriding

As discussed in the previous articles, a Scenario is comprised of a series of actions put together as steps. Each action may require parameters. Scenario provides values for these parameters via. test case. This is how data driven testing is realized in accelQ.

Scenario can also supply values for step parameters via. Parameter Overriding. This is a process where a parameter's value is fixed at the Scenario level, so these values cannot be varied at test case level. You use this feature when one or more of the parameters can just assume fixed values without requirement for variability.

For example, consider the following steps in a scenario:

1. Login to QBank (uname, password)
2. Navigate to Employee Records
3. Verify Employee Record (emp ID)

In this scenario, an admin logs in to the QBank application and verifies the records of a given employee. Here, we would like the scenario to run against multiple employees (data drive). However, for every iteration, you could login with just one admin user ID and password. There is no need to change the userid and password for every test case. You simply override username and password with fixed literal values.

Overriding with a fixed value

You can override a parameter with a fixed value for all test case iterations. To override a parameter, click on the parameter in the scenario workflow. Select appropriate option to override with. 

Following types of fixed values can be passed

• Literal: Just type the value literally
• Global Property: Value is used from a Global Property. Note that you can then supply information specific to a given Application Environment.
• Run Property: When you override with a Run Property, user is asked to provide this value at the time of test execution.

Note: When you are creating a new test case, overriden parameters are greyed out in the Test Case modal, so that you cannot change its value. Any updates to this value should be done from the Scenario workflow.