Input Parameters need data
When you define input parameters for an Action, you are essentially variabilizing the data in your Action logic. When you use this Action in a Scenario, it is required to provide values for these parameters so that Action logic can resolve the variables when running. Same goes when this Action is "called" by another Action. Parameters required for the "called" Action must be supplied by the "calling" Action.
When you create a Scenario, you supply the values for various parameters in the form of Test Cases.
Scenarios and Actions that are using a given Action are called its "references".
Change Impact when new Parameters added to Action
When you add new input parameters to an existing Action, there is a potential change impact on its referencing entities. Consider this Action was used in 4 other Scenarios already in your project. For all the currently existing parameters, these Scenarios must have provided values in various test cases. But the newly created parameter's data will be missing in the Test Cases, and will require updating all the dependent Scenarios with the values for new parameters.
Similarly, for all the Actions where this Action was being "called", we need to furnish values for the new parameters.
To facilitate ease of this update, ACCELQ presents a change-impact workflow as soon as a new parameter is added to an Action.
Providing initial values for new Parameters
This workflow is kicked-off as soon as a new Parameter is added to an Action. You may provide an initial starter value for the new parameters which will be inserted in all the referencing Scenarios and Actions. You may also chose to manually update these values for each Scenario.
With respect to referencing Scenarios, you can set a parameter value either in the form of a Test Case or overridden at the Scenario step level.
You may also review the list of dependent Scenarios/Actions and copy to clipboard for offline updates.