How-to: Create a Tricentis Tosca Test Configuration in SAP Solution Manager 7.2
As consultants we may all know that software tests in big implementation projects have to be repeated often during development cycles to ensure the quality. Optimally tests should be repeated every time the source code is modified and obviously repeating tests manually is costly and time consuming. Even though ECATT and CBTA (Component Based Test Automation) comes automatically for free with SAP Solution Manager 7.2 (SAP SolMan) and is tightly integrated with it, it is pretty powerful and broadly used at customers for many years. At this point it must also be said that CBTA has some limitations especially when it comes to cloud products like SAP Ariba and SAP Concur for example. Therefore we have seen some customers deciding to make use of other more powerful test automation tools for their tests like with Tricentis Tosca.
Tricentis, the global leader in continuous testing platforms, strengthened its strategic partnership with SAP recently. The partnership with SAP is based on Tricentis’ market-leading position in test automation and proven track record of helping SAP user companies achieve rapid SAP releases. Tricentis Tosca is integrable with SAP Solution Manager 7.2. In order to use Tricentis Tosca with SAP Solution Manager 7.2 the technical integration need to be performed first. Together with my colleague Lukas Goethel we invested some time to get into Tricentis Tosca and the integration with SAP SolMan 7.2 and are happy to share our two contiguous blog articles guiding you through all the steps you need to get started with Tricentis Tosca and SAP Solution Manager 7.2. So, if you are interested in integrating Tricentis Tosca with your SolMan, please have a look at the following blog article by Lukas Goethel.
After a successful integration of Tricentis with SAP SolMan 7.2 you can start creating test configurations in SAP Solution Manager 7.2.
In this blog post I want to share particularly how the process of scripting a SAP Fiori application with Tosca looks like. I will show you how you can add a SAP Fiori Executable manually to the Solution Documentation and start subsequently the scripting with Tricentis Tosca. This blog post is divided in 6 sections:
- Preparation: Adding a SAP Fiori Executable
- Create a Test Configuration
- Launching Tricentis Tosca
- Using the Test Configuration Parameters in Tricentis Tosca
- Add Executable Information to Tricentis Tosca
- Save and Go To SAP Solution Manager
To be able to create a test configuration it is necessary to add an executable to the respective node where you want to add your Tosca script in the Solution Documentation.
In case the needed SAP Fiori Application is not in the execution library, you can easily add it manually to your solution. Therefore please see my previous blog post under section ”Preparation: Add a Fiori Executable”
Please note at this point, that the executable information is not transferred to Tricentis Tosca, but adding the executable to a test configuration is mandatory. More on that will be discussed later on in this blog post.
After adding the executable, we can now use it in an automated test. For this, we need to navigate to the respective process step (in our case: “PS_Create_Incident”) and add the executable before creating a test configuration. Perform a right click in the elements area and choose “New” –> “Executable”. Search for the recently added executable and click on “OK”.
After adding the SAP Fiori Executable in the desired Solution Documentation node, we can create a test configuration. Therefore, perform a right click in the elements area again and choose “New” –> “Test Cases” –> “Test Configuration (Create)”. You should be able to see under the Test Script dropdown menu the option “Tricentis Tosca”. If this is not the case please have a look at the blog post of my colleague Lukas Goethel explaining the integration steps for SAP SolMan 7.2 which need to be performed.
Fill out the necessary fields and click on “OK”.
Make sure that all the necessary fields like “Target System”, “Executable” and “Test Profile” are filled out. In case they are not, navigate to “Goto” –> “SUT Management” and check the sections “Technical Destination” and “Business Destination Enhancement Details”.
Side note: The technical data of the test configuration will be transferred as “Test Configuration Parameters” to Tricentis Tosca.
Especially check and edit if necessary under section “eCATT and Third Party Tools” your Test Profile and Destinations. If you need further information on “Creating Test Profiles” please have a look at the official SAP documentation here.
To start Tosca and start scripting first make sure that your SAP Logon is open and you are logged in with your user (not the technical user). Simply click on “Launch Tricentis Tosca” on your test configuration to start the Tosca Commander. After a few seconds you’ll see under the tab “Test Cases” the name of your created test configuration. Now you are good to go to start scripting with Tricentis Tosca. Please note, that in this blog post I will not explain in detail how Test Cases are created, since this would go beyond the scope of this blog post. Feel free to have a look at the official Tricentis Tosca documentation regarding planning creating and maintaining Tricentis Tosca Test Cases here.
Using the Test Configuration Parameters in Tricentis Tosca
You can use the transferred Test Configuration Parameters from SAP SolMan 7.2 such as Client and SID and build it in your Test Case.
For instance: You may need to change the SID and Client information (depending on the selected branch etc.) in your link to the respective application as in our example, to the Incident Application. Therefore, you can pass the information of the Test Configuration parameters to your link to the application.
Here an example:
As mentioned before the executable information from the Test Configuration in SAP SolMan 7.2 is not transferred to Tricentis Tosca. So how can we feed Tricentis Tosca with this needed information?
You can make use of the “Test Parameters” in Tricentis Tosca and pass information as “Input” from the Test Configuration.
To achieve this simply perform a right click on your Test Case and navigate to “Edit Test Parameters”. You will be asked to enter your Solution Manager credentials.
Add a name for your parameter and enter the default value you want to pass as an “Import” Parameter. In our case we are using the Object and Action parameters which we already used while creating our executable in the Solution Documentation (Default value = <Object>_<Action>).
With this we can easily edit our link to the application and use this parameter to navigate to the expected application.
After creating your Test Case you need to save your changes and go back to SAP Solution Manager 7.2.
Therefore, perform a right click on your project folder and select “Resume Remote Control” and click “Save and go to SAP Solution Manager”.
After going back to your Test Configuration you will also see under the tab “Parameters” the “IMPORT-Parameter” we’ve created in Tricentis Tosca.
This is it! As you can see it is easy to benefit from the advantages of integration between Tricentis Tosca and SAP Solution Manager 7.2. Now it’s your turn and try it out by yourself! Happy testing 😊
If you want to integrate your SAP Solution Manager 7.2 with Tricentis Tosca then have a look at the following blog post: