Adapting Test Automates with the Test Automation Tool

The Manage Your Test Processes app is where you view the standard test process automates, and create your own custom test process automates. Within the app, there are three types of test processes:

• Standard test automates/processes that are created and delivered by SAP to align with the manual test script for the SAP Best Practices business process. Standard automates cannot be edited or deleted.
• Custom test automates/processes that are copied from a standard process or built from scratch.
• Post upgrade test automates/processes that are created and run by SAP on behalf of the customer after a release upgrade.

To align a standard test automate with a customized business process, first make a copy of the standard process. All further edits should be made in the copied process. After the process is copied, the type changes to custom, and by default, the process is not visible in the Test Your Processes app. After making your edits to the process, you can change the visibility to make the process available to be assigned to a test plan.

1. Select the Edit button to choose which process step (test procedure on the test script) you need to change.
2. Select the checkbox of the process step and choose Change Type to make the step custom (instead of standard). In the Release Compatibility column, the checkmark changes to a question mark, which indicates this process step will need to be validated after each release upgrade.
3. Select Save.
4. Click the custom process step to view the individual actions. These correspond to the test steps on the test script. Select the Editbutton in the lower right corner.
   • Actions that are not optional (slider set to NO) are mandatory when executed in a test plan. If there is a failure on any mandatory action (e.g. if the value you've set up in the test process to select isn't available to choose), the entire test plan stops at the failed action and does not continue to the run any actions that follow it.
   • Some values are bound to others because the selection of one field (e.g. United States) determines the options available to choose in another field (e.g. List of states within the U.S.).
5. In this example, we added some custom fields to the UI of the Create Customer Projects app, and want to capture those additional fields within the test automate. I look through the list of actions and select the checkbox of the action where I want to add my custom action above or below.
6. A new browser tab will open with the actual Create Customer Projects app. I navigate back to the original tab to select Record, which begins the screen capture of my keystrokes on the browser tab with the Create Customer Projects app.

Learn about the features of the Manage Your Test Processes app in this tutorial.

On the new browser tab, I see a Recording Panel that includes buttons for Check, Read, Stop, and Pause. Click through the app as you normally would to capture your custom keystrokes. The Check and Read buttons should be used in specific use cases:

• Use the Check button when trying to capture a value, error message, or label that is static on the screen.
• Use the Read button when trying to capture a value or non-error message on the screen.

For both the Check and Read buttons, the value or text captured when you pressed the button is stored as a variable or parameter that can be used later for data binding. Data binding passes the data read from one executable action to another action. During test execution, these values are validated. If the value or text captured during test execution does not match what you captured when editing the actions of the process, the action step will fail. If the action is mandatory (not optional), the entire test will fail at this step.

After capturing my keystrokes, the tool generates the relevant actions and the values I selected (e.g. select field, choose value, etc.). When finished, I can save my changes and change the visibility of the test process so it can be added to a test plan.

Learn more about managing your test processes in the SAP Help Portal.

Learn how to adapt SAP Best Practices test automates in this tutorial.

To ensure there is always data available to run test processes with, you can bind the process to a Test Data Container (TDC). These are containers of reusable sample data relevant for different fields within business processes. Test data containers can serve as a single source of test data to ensure a test process doesn't fail in execution simply because there wasn't any available data to fetch. There are standard TDC available and you can create your own custom TDCs.

Learn more about Test Data Containers in the SAP Help Portal.

Learn how to create a test data container and it's variants in this tutorial.