Test Objectives
There are three key elements, namely ‘Functionality Testing’,‘Roles & Authorization Testing’, and ‘Sprint Cycle Test Planning’, each of which is explained in this interaction.
Click on each of the options to reveal an explanation.
Testing Mapped to the SAP Activate Roadmap Phases
Tests are conducted at various stages of the implementation project, with different purposes and objectives. Select the numbers 1, 2, and 3 below to learn more about Implementation Tests, End User Acceptance Tests, and Regression Tests.
Roles and Responsibilities for Testing
Click each role below to reveal the description and responsibility.
Formal vs. Informal Testing
Informal testing is not recorded or eligible for sign-off. This is often the case where test variants are likely to be so numerous that logging each would add an excessive amount of time to the task. Unit and string tests are examples of informal tests.
Formal testing refers to tests that require formal documentation of their completion status in SAP Cloud ALM. Business process tests, systems integration tests, and user acceptance tests are examples of formal tests.
Testing Activities after Go-Live
After a customer is live, a release upgrade or activation of new business processes makes it necessary to test the processes again to validate their functionality. Activating scope for a new country will require the type of unit, string, business process, integration tests and others that were completed in the Realize phase during implementation. All other testing triggered by changes to the system is considered regression testing since it requires a re-test of functionality or roles and authorization tests that were already passed. Regression testing can be completed much faster with the Test Automation Tool for SAP S/4HANA Cloud.
There are two primary types of tests managed by the Test Automation Tool and a third manual test:
Test | Description |
---|---|
Post-Upgrade Testing (Automated) | A customer may grant SAP permission to carry out Post-Upgrade Testing (PUTs) on their behalf using the Test Automation Tool. If permission is granted and the prerequisites are completed, SAP will automatically execute post upgrade test scripts in the customer's Test system and the customer can review the completed test results to address any issues. PUTs are typically unit or string tests, but do not typically cover entire business processes. |
Customer Testing (Automated) | A customer can use the Test Automation Tool to run automated scripts that align with the SAP Best Practice business processes. If a customer-specific configuration prevents the usage of the standard test process, the customer can make a copy of the existing process and customize it. Customers can also create entirely custom business processes from scratch with the tool. |
Regression Testing (Manual) | If a predefined automated test script is not available or viable, customers can use SAP Cloud ALM Test Management to build and track completion of manual test cases. |