When test assets are shared across different projects, seamless change management is extremely important. Updates to a shared test asset on the publisher side may require corresponding reconciliation on the subscriber side. ACCELQ adopts a comprehensive change-management workflow to make this process seamless and intuitive.
Life-cycle related changes
Following life-cycle-related changes on the published Action are handled as described.
Unpublish Action: This is blocked if any of the subscribing projects are using the published Action. Delete Action: Same as above.
Deleting a Project: Deleting a Project that offers published Actions is blocked if there is at least one Action from the Project which is used in a subscriber Project.
Turning off Publish flag in project admin: Turning off the publish flag in the project admin is immediately accepted. This prevents any new subscriptions to this Project. However, the projects that already subscribed to this project will continue to have access to the published Actions.
Changes to Published Action
Changes to Action logic are automatically accepted and become effective in real-time. Subscribing projects will start exercising the new logic with immediate effect. However, some changes may require user intervention on the subscribing Project.
If the Publisher Project makes changes to published Actions that require user intervention, an alert is indicated at the Project name button in the top toolbar. Click on the alert and follow the steps to resolve the change impact. Typical impacted items include change of parameters, the addition of new Inputs/Outputs, etc. of the published Action.
Please sign in to leave a comment.