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.
When you create a new Scenario, you supply the values for the Action input parameters in the form of Test Cases.
However, when a new parameter is added to an Action that is already part of an existing Scenario, all the Test Cases for that Scenario must now be updated to provide values for this new parameter.
The same goes when this Action is "called" by another Action. Parameters required for the "called" Action must be supplied by the "calling" Action.
Change Impact when new Parameters added to Action
Referencing Scenarios and "calling" Actions need an update when a new Input Parameter is added to an Action used by these entities.
To facilitate ease of this update, ACCELQ presents a change-impact workflow as soon as a new input 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 choose to skip and later manually update these values for each Scenario separately.
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 it to the clipboard for offline updates.