8
Currently, there is no audit documentation/proof that comes out of the RSAT tool for the entire test suite that can be used for SOX/Audit documentation and compliance purposes to prove out the test steps and scenarios executed and the transaction numbers generated.

Ideally, this documentation will have screenshots so auditors don't have to understand the RSAT tool and Devops and instead just get this documentation that clearly outlines (ideally screenshots of the steps) the test suites and steps executed with the generated transaction numbers such as PO number, receipt number, AP invoice number etc., in a P2P cycle.

It takes a long time right now to put this documentation together and sometimes we are better off with manual testing.

Please add this feature
STATUS DETAILS
Needs Votes