SAP Cloud ALM: end-to-end user journey for testing process of S/4HANA Cloud
In this blog post we will describe testing phase of SAP S/4HANA Cloud 3SL Implementation or Upgrade projects. To start described activities following pre-requisites are necessary:
- All 3 tenants (DEV – TEST – PROD) of SAP S/4HANA Cloud are provisioned;
- Integration between SAP S/4HANA Cloud, SAP CBC and SAP Cloud ALM is set;
- Test data (both master and transactional) are available in SAP S/4HANA Cloud TEST tenant;
- Unit tests are done in SAP S/4HANA Cloud DEV tenant.
Before we start our journey, let´s highlight small piece of theory. During the testing activities we need to separate 3 types of tests:
- Unit tests are the smallest and simplest testing activities, which have to be performed by developer/configuration expert right after implementation of certain functionality in DEV system;
- Test automates are pre-delivered by SAP for certain solution processes, and can be launched either from SAP S/4HANA Cloud or from SAP Cloud ALM. Results are to be documented in Cloud ALM;
- Manual test cases imply sequence of actions in SAP S/4HANA Cloud, during which correctness of business operations to be checked. Results are to be in SAP Cloud ALM.
Preparation to the testing activities
First of all it is necessary to identify test scenarios – pick basic processes & minimum requirements for the project to succeed. To document this, it is recommended to use Requirements application of Cloud ALM:
In the next step it is necessary to perform pre-requisite to work with SAP S/4HANA Cloud test automation tool – set up users for the test automation tool. Technical details can be found in SAP Activate Roadmap.
Once it is done, we need to access the SAP S/4HANA Cloud application Manage Your Test Processes to review and adjust available test automates. Accelerator, available by the link at this SAP Activate roadmap step can be helpful for this activity, as it contains full and updated list of all available test automates.
After the synchronization we can proceed with import of relevant automated test cases´ content in Cloud ALM in the same application:
Now we need to create manual test-cases. It is possible to create every test case from the scratch and describe it in Cloud ALM:
Another option is to import Test Scripts from the SAP Best Practice content for SAP S/4HANA Cloud into SAP Cloud ALM, how described in this SAP blog post.
When all tests are created, they have to be assigned to requirements and user-stories. Please, refer to this SAP blog post for the detailed information about the procedure.
The last and quite obvious step of this phase is to set all created tests to “Prepared” status in SAP Cloud ALM:
So now we have 2 types of tests ready to be used: automated and manual.
For automated test-cases we trigger their execution from Cloud ALM Test Execution application:
Once the run in SAP S/4HANA Cloud of such test-case is finished, results will be available in the same application of SAP Cloud ALM.
Manual test cases have to be executed accordingly their descriptions (available in SAP Cloud ALM) in SAP S/4HANA Cloud, and the results to be documented in SAP Cloud ALM.
In case error identified during test execution, defect to be created (in Cloud ALM Test Execution application) and followed-up:
If defect requires SAP Support, it is necessary to open incident in Service Now system.
Once issues are resolved, defects get closed and retest is needed.
Additional information about defect management can be found in this SAP blog post.
The logical step after testing procedure is to move transport requests, which contain tested changes from SAP S/4HANA Cloud TEST tenant to PROD tenant.
This should be done via SAP S/4HANA Cloud ATO tools:
Firstly we move transport requests to PROD system buffer and import them then to PROD system itself.
In the next SAP blog post we will extend the process with 3rd-parties tool, which can also be integrated in the testing flow.
Will there also be a similar scenario for the private cloud environment in the future?
it is possible to do automated testing for S/4HANA Private Cloud via Cloud ALM as well, if I am not mistaken.
Currently we have S/4 Test automation which is integrated with SAP Cloud ALM. This is available only for Public cloud. All the standard automated test processes will be synchronized to SAP Cloud ALM.
We will have Tricentis test automation tool which will be integrated with SAP Cloud ALM.
The Tricentis Cloud Automation Test for CALM has not released yet. We will announce it when it is released (most likely in Q1 2023, this is the the current status and may change).
Thank you very much for that overview - I like that it includes the end-to-end scenario.
What would be really nice is some advice on how to handle the test data management. Through the upload of the best practice content from the best practice explorer to Cloud ALM, there is quite some reference to data already in the test scripts and it is a lot of effort to adapt that manually for each step - surely there is a more convenient way to handle this?
Currently there is no test data management capability within SAP Cloud ALM. I feel its better to keep test data independent of test case as test case can be tested with different sets of data. Wrt S/4 Test automation tool which is created with SAP Cloud ALM, test data is handled through test variants within the test automation tool.
Hope it helps.
thank you very much for your reply. Your answer helps me indeed.
However I am not sure if I understand you correctly. I agree with you that generally it is more convenient to separate test cases and test data. However in the best practice explorer content for the test case upload in ALM, the test cases do refer to some demo data e.g. org data like shipping points etc. So when uploading the test case, all this data get's added in the description for the tester as well, which is very inconvenient since we either have to manually remove the references or manually change them in all test steps to the actual data we want to have tested.
I now understood there is no solution to it, but still I would like to emphazise that it would be a nice to have a feature for it indeed.
Thank you so much.