...
Step 1 | Enter any data in Field1 and click Submit. |
Step 2 | Check the Data Report in transaction /n/IQX/FAB_DATA. Enter the Form Name and click Execute. The data has been submitted. The current status is Approval and the next approver is FABAPPR1. |
Step 3 | Log in to the application as the Approver. Go to My Forms → To Approve. Open the application and select Approve. |
Step 4 | Refresh the Data Report in transaction /n/IQX/FAB_DATA. The current status is Update SAP and the next approver is WF-BATCH. |
Step 5 | Go to transaction SM37 search for Jobs with a similar name as the application. |
Step 6 | Refresh the Data Report in transaction /n/IQX/FAB_DATA. The Current Status is now Completed. The Header Changes show the history and the Log shows all the relevant log entries. The field Result holds the random number generated from the class. |
Step 7 | Check the results from the application. Log in as the Submitter. Go to My Forms → Submitted By Me. |
Negative Testing
Step 1 | Go to Code to open the Form Life-Cycle dialog. In the Form Life-Cycle dialog, select the button ABAP Routine next to the Perform System/Background Task to open the Class editor. Use the following logic in method PERFORM_SYSTEM_TASK. For testing purposes, set the value of parameter E_SUCCESS to ABAP_FALSE.
| |||||
Step 2 | Repeat Steps 1 to 5 from the Positive Testing guide. In transaction SM37, the job logged a Failure message. | |||||
Step 3 | Check the Data Report in transaction /n/IQX/FAB_DATA. Enter the Form Name and click Execute. The Current Status is now Administrator. The errors are included in the Log. The Administrator defined in transaction /n/IQX/FAB_CONFIG or in method DETERMINE_APPROVERS_FOR_ROLE can rectify the issue or and resubmit the Form. |
Debugging and Troubleshooting
...