Provide Consent for Post-Upgrade Testing
The customer needs to explicitly provide consent for SAP to run post-upgrade tests on their behalf in the Test Your Processes app. Navigate to the Post-Upgrade Tests tab, and select the badge icon to open the consent screen. After consent is provided for post-upgrade testing, SAP will execute the applicable standard test automates in the customer's system using test data automatically fetched from the customer's system, or from a Test Data Container. Post-upgrade tests (PUTs) are generally focused on business processes where the customer has made no customizations to the standard process, however SAP has been moving towards making PUTs more customer-driven with additional options to add custom scope and decide which test variant will be executed. The Manage Upgrade Tests app is where you find some capabilities to customize the PUT scope and assign data variants.
In some cases, PUTs cannot be executed on behalf of the customer. This could happen if the respective business process is not active, the data picking logic fails to fetch all the required data necessary for the automates, or the execution pre-check is failed. Other reasons could include not maintaining custom logic or custom field changes that have been made to an actual business process in the corresponding PUT automate, not maintaining the execution variant, or if the default test user doesn't have the necessary permissions to run the PUTs.
Triggering Post-Upgrade Tests
After consent has been provided, post-upgrade tests can be triggered from the play icon after a release upgrade. However, a test execution variant needs to be maintained in the Manage Upgrade Tests app in order for the post upgrade tests to run successfully. A series of system checks will be conducted before the tests begin, and as long as no issues are found with the pre-checks, the post-upgrade tests will then be executed for the relevant business processes.
Learn more about managing your post-upgrade tests in the SAP Help Portal.