Change impact when “sharing” is changed for an Action

Change Impact analysis of test assets is implicit in accelQ. When you try to change any aspect of a test asset, system automatically calculates the impact of such a change on its dependencies and allows the user to make a decision or take mitigating action.

Action sharing allows the same Action to be used across multiple Contexts. In a navigation rich Web application, it is common that a given functionality is accessible from multiple Contexts. In such a case, you could share an Action without having to duplicate the effort of Action logic development.

If a new Context is added to the Sharing list of an Action, there is no change impact. You are just introducing new capability into the application test flow. But if you are removing a Context from the sharing list, there is a potential change impact. If the Action was already being used in Scenarios as a member of the removed Context, it is exactly as if you are “deleting” the Action from this Context. System will point to all such instances of usage across Scenarios and ask the user for confirmation. In case the user proceeds with confirmation, appropriate alerts are generated in the affected Scenarios.