One of the most common questions which come from our customers is - Can we scope our custom automates in Post Upgrade Tests (PUT). The answer is Yes, the Manage Upgrade Tests App was a new addition to the SAP S/4HANA Cloud Test Automation Tool (TAT) suite which offers our customers the flexibility to customize the scope of their upgrade tests by adding custom automates
The MUT app serves as a preparatory step for the upgrade cycle where the scope is maintained and automatically triggered via the task list after every major upgrade. This makes PUT more customer driven and helps to identify defects earlier. Apart from enabling them to add custom scope, customers can trigger PUT from the Test Your Process (TYP) app at any point in the software lifecycle with a single click.
Requirements which paved the way forward
- Configure custom automates created using the Test automation Tool - Our customers may want to execute additional business processes which may not be part of the regular PUT scope.
- The upgrade test scope can be customized with a mix of SAP delivered PUT automates and customer specific custom automates.
- Focus on customer relevant scenarios as per the business model. Our customers may not want to execute the entire scope of PUT automates as some of them may not be relevant for them.
Building your test suite using the Manage Upgrade Tests App
Using the MUT app, you can create multiple regression test scope with execution variants. Each execution variant contains a combination of standard and customized scope to be triggered during PUT.
- Execution Variants: You can view, update, copy and delete execution variants comprising of an execution list which contains PUT processes and customer test plans. The execution variants can have names and descriptions for easy distinction. One execution variant is marked as default at any point in time. It is easily possible to create new execution variants by navigating to the PUT Processes and/or Customer Test Plans tabs.
- Execution List: If a previously created execution scope exists, it will be displayed in this view-only tab. Otherwise, it will be empty. A set of PUT processes get populated as the default execution list once the system setup is complete.
- PUT Processes: All the PUT processes relevant to your scope and which pass the pre-check are listed in this tab. We can run a Pre-check by clicking on the Run Pre-check button to populate the PUT processes which are active for the given customer system.
- Customer Test Plans: All Customer Test Plans with the last execution status along with the data variant name used for the latest execution will be listed in this tab. This is where we can add the custom automates.
Integration with Test Your Processes (TYP) App
Starting with the 2308 release, all the Execution Variants maintained in the MUT app will be available to for a PUT execution from the TYP application. Customers can select the ‘Execution Variant” from the dropdown and with one click trigger the PUT execution for the regression suite of their choice.
The Post-Upgrade Tests Execution History pop up displays the execution variant triggered and the scope of execution along with the status of the tests. The Track Post-Upgrade Tests option launches this pop up.
The source of the execution scope can take one of the following values-
- Executed with all relevant post-upgrade scope.
- Executed with Scope from Manage Upgrade Tests application along with the execution variant name.
Viewing results in the Analyze Automated Test Results App
We can apply the Test Plan Type filter to view the execution results in the Analyze Automated Test Results application. The execution scope as well as the execution variant can be selected from the dropdown to filter the results accordingly.
Further Helpful Links
Manage Upgrade Tests
Viewing filtered results in AATR
Blog Post on Test Data Container