In SAP GUI you often select an option in a transaction and the second time you visit that transaction your selection is remembered and you find the SAP window in the same state.
For example, under transaction ME21N the Document overview option is turned on by default. If you go to that transaction and click the 'Document Overview Off' button to switch it off, the next time you will visit this transaction your selection will be remembered and you will find the document overview panel switched off. Therefore, you are not always in need to switch it off. The button itself changes label from 'Document Overview Off' to 'Document Overview On'.
How does Qualibrate deal with execution of such steps?
Qualibrate offers a Mandatory/Optional toggle for steps under the Technical details pane/User tab. Once you set your step to optional, if the needed object is not identified the step execution will not be failed. Qualibrate will automatically move to the execution of the next step.
SAP GUI example
Step1. Record you steps in SAP:
- Go to transaction ME21N
- Press ENTER
- Click on Switch Off Document Overview
Your resulting Qualibrate task should look similar to:
Step2. Select Click on Switch Off Document Overview step and in the Technical details pane go to the User tab and set the toggle to Optional:
Step3. Save your configuration
The optional steps are are marked using yellow:
1. With Manual Tester
If you choose the Do it for me option of the Manual Tester on an optional step for an unavailable object the step will be grayed out and the execution will move to the next one. The Document Overview Off button is not available, you can find the Document Overview On button, therefore this step is skipped.
ObservationKeep in mind that the Manual Tester has a Skip button that you may use during execution to skip any kind of steps, mandatory or optional.
2. With Automated Tester
During automated execution, if the object is not available the execution will continue with the next step.
Under the Testing Logs section you will find the logs generated during test execution. Steps that are not executed will be logged as 'Skipped':