Authorization Failure Reason

The new authorization failure reason has been introduced to automatically detect scenario’s where in the recording a transaction was able to be run by the given user, but in the playback the same object cannot be run as the user is no longer authorized.

Example Scenario

A common scenario for use of this scenario in regression test cycles is when authorization changes are being introduced either knowingly or unknowingly. If there are hundreds or thousands of users to be managed and a rationalised list of common roles, then a small change to alter permissions can have a drastic effect on users once the change is promoted to production.

*This applies to all object types not just SAP GUI dialog transactions. It covers batch jobs, inbound RFC calls and inbound web-services. In the next release, this will be extended to Fiori apps where users are no longer able to start their apps or execute functions within the app.

Process

All authorization failures will be detected automatically by Testimony during the playback for all object types. When a failure is detected by Testimony in the playback, the last authorization failure for the given user is checked by the playback engine and its details stored.

*The failure reason will be accessible from the playback overview and from within the test script view for the execution queue. It is also visible within the new investigate screen.