Utilizing Post-Upgrade Tests in the Test Automation Tool

Objective

After completing this lesson, you will be able to provide consent for post-upgrade tests conducted by SAP

Post-Upgrade Tests

Provide Consent for Post-Upgrade Testing

The customer needs to explicitly provide consent for SAP to run post-upgrade tests on their behalf within the Test Your Processes app. To do this, navigate to the Post-Upgrade Tests tab and select the badge icon to open the consent screen. Once consent is granted, SAP executes standard test automates in the customer's system. These tests use data automatically retrieved from the system or from a Test Data Container.

Post-upgrade tests (PUTs) focus on standard business processes without customizations. However, SAP is increasing flexibility by allowing customers to define custom scopes and select specific test variants. You can use the Manage Upgrade Tests app to customize the PUT scope and assign data variants.

Screenshots showing how to provide consent for post-upgrade testing by SAP.

In certain scenarios, PUTs cannot be executed. Common reasons include:

  • Inactive business processes
  • Data picking logic failures
  • Failed execution pre-checks

Other issues may arise if:

  • Custom logic or custom fields are not maintained in the PUT automate
  • The execution variant is missing
  • The default test user lacks the required permissions

Triggering Post-Upgrade Tests

Once consent is provided, you can trigger post-upgrade tests using the play icon after a release upgrade.

Caution

A test execution variant must be maintained in the Manage Upgrade Tests app for the tests to run successfully.

The system performs a series of pre-checks; if no issues are found, the post-upgrade tests will execute for the relevant business processes.

Screenshots showing how to trigger post-upgrade tests.

Learn more about managing your post-upgrade tests in the SAP Help Portal.

Try it yourself!

Learn how to trigger post-upgrade tests in this tutorial.