Implementation projects involve various tests at different stages to meet specific objectives. The three primary types are:
- Implementation tests
- User acceptance tests (UAT)
- Regression tests
Implementation testing takes place during the Realize phase of SAP Activate. Partner LoB configuration experts configure processes in the development system’s customizing tenant and transport the settings to the test and production systems.
Testing begins during configuration:
- A unit test validates one component of a business process.
- A string test validates several connected components.
- Business role testing confirms that users have the correct access to data and functions.
- An end-to-end process test validates the complete process.
Note
When a setup instructions document is available in SAP Signavio Process Navigator, complete it before the test script. It often contains integration or initialization activities required for the test prerequisites.
Unit and string tests are generally informal. Formal testing should take place in the SAP S/4HANA Cloud test system after integrations are connected and data has been migrated, creating a more realistic environment. End-to-end process, integration, and data migration tests must be documented using SAP Cloud ALM Test Management. A formal test may cover several business processes performed in sequence.
User Acceptance Testing
User acceptance testing also occurs during the Realize phase. Ideally, it is performed by the customer LoB experts who participated in the Fit-to-Standard workshops. Because they helped identify the original requirements, they are well positioned to confirm that the configured solution meets the business need.
Partner configuration experts create manual test cases in SAP Cloud ALM Test Management. Customer experts execute the procedures in the test system and document their results in Cloud ALM. All issues should be resolved and recorded before the project moves to the Deploy phase.
Regression and Upgrade Testing
Regression testing usually takes place during the Run phase after go-live. Its purpose is to identify whether a release upgrade affects the customer’s configurations or customizations. The customer is responsible for regression testing if they've already gone live, but the Test Automation Tool can automate much of the work.
When an upgrade occurs during implementation, the partner team must test the configured processes against the new software version before continuing. Customers can also consent to SAP running automated post-upgrade tests for standard, unmodified processes.
Partner experts should create or update test automates as each business process is configured. When custom logic changes a standard process, its automated test must be updated accordingly. These automates can then be run in the test system during upgrades instead of executing every test manually. After go-live, customers use their own automates for customized processes and SAP post-upgrade tests for standard processes.
Note
Use the Scope and Dependencies spreadsheet to plan your testing activities. You can find it in SAP Best Practices for SAP S/4HANA Cloud Public Edition→ Accelerators→Getting Started→Availability and dependencies of solution processes.