Subscription: Enterprise Edition Availability: Release 6.0
Cross-project asset sharing is a powerful enterprise capability to allow sharing of Actions and related resources between multiple Projects. Recall that in ACCELQ, a Project usually corresponds to one application-under-test (AUT) where you manage all the test assets related to the specific AUT.
However, when you are building end-to-end system-level automation, there may be a need to bring test assets from multiple applications in one flow. Different teams may be responsible for the automation development and maintenance of each of these applications. It is not ideal to duplicate these test assets in the end-to-end project. Cross-Project sharing allows independent teams to work in their own Project/Application silos while still allowing the possibility to build end-to-end automation that cuts across multiple applications.
ACCELQ accomplishes cross-project sharing using a Pub-Sub (Publisher-Subscriber) design pattern. A Project may publish one or more Actions that become available to other Projects in the Tenant when subscribed to this Project. Changes, updates, and ongoing enhancements for the published Actions are completely managed by the Publisher.
A Project can subscribe to one or more other Projects in the Tenant and all the published Actions from these Projects become available locally. You can use these Actions in Scenarios and Actions (call-Action feature) just like you would do for a locally defined Action.
While the core logic, element identification, etc. is fully managed by the publisher, ACCELQ allows the subscribing Project to configure the relevance of the Action as suitable for the local Project. This makes sure the subscribed Action completely behaves like a locally defined Action without placing any artificial constraints.
As the published Action undergoes updates, a comprehensive change-management workflow ensures that the changes are onboarded to the subscribing project seamlessly. There may be various types of changes on the published Action, some of which could be just for "review" while others could require an "update/action" on the subscriber side. An extensive alerting mechanism on the subscriber project guides the user through the reconciliation of these changes.