Basis Technologies strongly recommend that our customers thoroughly test their ActiveControl setup fully before go-live.
Basis Technologies does not provide Test Scripts as part of an Implementation (or subsequent Upgrade) of ActiveControl, this is a customer responsibility.
We find that our customers perform very different levels of testing, depending on the scope of the ActiveControl implementation and the extent of their existing SAP estate and Change Management processes.
Wherever possible, this should involve moving SAP transports through each ActiveControl path, to test the workflow and approvals you have configured within ActiveControl.
At an absolute minimum, Basis Technologies would recommend that the following scenarios are tested:
| Suggested Test | |
|---|---|
| 1 | Run test transports through all systems to ensure that all is working correctly and as expected. Check Imports, Skipping Rules etc |
| 2 | Test Workbench and Customizing transports end to end. |
| 3 | Test Approval process. |
| 4 | Test all key Analysers Including Overtake / Conflict Analysis etc |
| 5 | Test Email notifications (including link from Web interface). |
| 6 | Test Web interface (operation, approvals, analysis, etc.). |
| 7 | Test creation of Manual Steps / Manual Activities. |
| 8 | Test user access and roles / authorizations. (especially if using copied Z roles) |
| 9 | Test transport Backout process. (if relevant) |
| 10 | Test Merge process (if relevant) |
| 11 | Test In-line conflict analysis. (if relevant) |
| 12 | Test user exits / enhancements. (if relevant) |
| 13 | Test any existing Integrations – between your non-Production DC and a non-Production Integration instance. |
Basis Technologies recommend involving the intended end-user community in the testing process of ActiveControl, to ensure early familiarity with the tool and buy-in to the to-be processes, prior to Go-Live.
Post your comment on this topic.