Setting up Third-Party Test Automation Tool with SAP S/4HANA Cloud
With the new age of rapid ERP implementation approach, fueled by agile implementation methodologies like SAP Activate, the quality of your implementation journey can only be met by following simple yet crucial strategy adoption of “Test Driven Implementation.” You may find various definitions of test-driven implementation and how to achieve it. Yet, you can explain it in just one line ‘The desire to drive Quality Assurance as early as possible in your implementation journey.’
The competent QA expert can easily see the value of identifying the correct Testing Automation Tool early in the project phase and bringing it into the test planning phase of the project.
When we talk about the Testing Automation Tool in the SAP S/4HANA Cloud implementation project, the obvious choice that may pop up in your head is SAP S/4HANA Cloud Test Automation Tool. The test tool comes natively as part of the SAP S/4HANA Cloud Quality System and offers seamless integration with SAP Cloud ALM; We have some goods accelerators and blog posts explaining how we can use Test Automation Tool; please click here if you want to learn more.
However, the Test Automation tool is only available for the SAP S/4HANA public cloud edition and not for the private cloud. This limitation eventually leads some customers to consider having a third-party testing tool to support their testing journey.
Regarding third-party testing tools for SAP S/4HANA Cloud, SAP has partnered with the Tricentis Testing tool as SAP Solution Extension. Tricentis provides a modern Testing automation tool called SAP Enterprise Continuous Testing by Tricentis (ECT)– The product name at Tricentis is Tosca. It can automate any SAP Screen, be it a traditional GUI based or a modern Fiori-based user interface.
Enterprise Continuous Testing follows a module-based test automation approach where the screen or business process flows are captured as a module. The following snapshot can give you a fair idea of how you can scan various pieces of the business process into modules; in this example, QA specialists have captured the checkout process in 7 different modules:
These modules or a subset can be connected in a logical sequence to prepare the Test Cases. In our example, assume that the test case scope only covers five modules from the checkout process, then the QA specialist can easily reuse just 5 of them and use them in the test case design.
This modularized testing approach is the solution for all the gridlock you may face with the traditional script-based automation tools.
Firstly, Tosca’s module-based tool follows a no-code approach. It makes testing much more flexible for non-technical users. Secondly, maintenance of the test cases is straightforward. As the test cases are nothing but reused modules chained together, if there is any change in the front-end module, you can fix it by just rescanning the changed module.
You can find more details about Tricentis Tool here: SAP Community – Search on Tricentis Tag.
Follow the SAP Activate community!
Check out the SAP Activate Minutes for weekly quick learnings on SAP Activate-related topics.