Testing

Overview of Testing

See Overview of Oracle Approvals Management.

To ensure your transaction type applies appropriate rules to each of your business cases, you create test transactions on AME's Test Workbench, or 'real' transactions in the integrating application. You can select a real transaction and create a test case from it for future testing or create the initial test case. You can store the simulated and the real transaction test cases for future reference.

The Test Workbench displays a list of previously defined test cases. You can select an existing test case and have AME treat this as a real transaction to determine the active rules and the final approver list. By copying a test case, you can have many variations on a standard transaction. This enables you to exhaustively test your approval setup. When defining or updating a test case, you can supply values for the attributes of interest. For the test case, it is possible to define header values and if appropriate create detail lines in order to mimic an invoice for example. The Test Workbench enables you to check for item level, approver level, and transaction level productions. In addition, it displays the attribute values for the subordinate items in a transaction. For debugging and testing, you can see the various stages of the approver list.

Planning Your Test Cases

While planning you implementation strategy, your implementation document, showing your approval policies, should specify test cases sufficient to verify that your transaction type does the following things according to your business rules:

You can do most of your testing using the Test Workbench. You may also use SQL*Plus and the integrating application to test certain aspects of your implementation.

Testing Your Approval Rules

Use the Test Workbench tab to perform either real-time or simulated tests for the given approval rules setup of a transaction type. Using the Test Workbench, you can do the following: