From this article you will learn:<\/h2>\n\n- What SAP API is<\/li>\n
- What does it mean to test the SAP API<\/li>\n
- How to quickly build test cases<\/li>\n
- How to run all test cases from a single platform<\/li>\n
- How to integrate Int4 IFTT with Tricentis Tosca<\/li>\n<\/ul>\n<\/div>\n
\n<\/div>\n
In his latest book “Enterprise Continuous Testing: Transforming Testing for Agile and DevOps” Wolfgang Platz mentions that API testing is the future of automated testing as it is the only part of enterprise system testing where in reality you can automate >85% of test cases.<\/p>\n
<\/p>\n
What is SAP API in reality?<\/strong><\/h2>\nMost of the companies which use SAP use asynchronous (IDOC, Proxy) integration scenarios for their B2B partners or legacy systems. Most of those message exchanges however are using SAP middleware products like SAP Process Orchestration (SAP PO) or SAP Cloud Platform Integration (SCPI).<\/p>\n
What does it mean to test the SAP API?<\/strong><\/h2>\nThere are many use cases but the most common ones are:<\/p>\n
– SAP Process Orchestration (SAP PO) upgrades, patching or migrations
\n– non SAP middleware to SAP Process Orchestration (SAP PO) migrations
\n– SAP Process Orchestration (SAP PO) to SAP Cloud Platform Integration (SCPI) migrations
\n– continuous testing of SAP Process Orchestration (SAP PO) or SAP Cloud Platform Integration (SCPI) integration flows
\n– SAP Application Interface Framework (SAP AIF) testing
\n– testing IDOC, Proxy scenarios at the S\/4HANA (or any other SAP backend) system<\/p>\n
How can we quickly build test cases for those use cases?<\/strong><\/h2>\nInt4 IFTT is the only Native SAP certified testing tool which fully supports all of the above use cases out of the box. Due to the nature of asynchronous integration and Int4 IFTT<\/a><\/strong><\/span> prebuild accelerators, test cases for all use case can be implemented in days\/weeks and not in months as with other software which is not designed specifically for SAP API testing.<\/p>\nMore information about testing SAP application integration scenarios can be found in our free openSAP<\/strong> course: Virtualize and Automate Your SAP Testing Using Int4 IFTT<\/a><\/p>\nCan we use test SAP API with Int4 IFTT from Tricentis Tosca?<\/strong><\/h2>\nInt4 IFTT is a complementary product to Tricentis Tosca and you can easily run all of your test cases from a single platform (like Tricentis Tosca). In order to do that you can call Int4 IFTT api directly from Tricentis Tosca as shown in the example below and analyse the results of all types of testing in a single tool.<\/p>\n
How can we integrate Int4 IFTT with Tricentis Tosca?<\/strong><\/h2>\nBelow you can find a simplified example on how to run Int4 IFTT from Tricentis Tosca. For Int4 IFTT configuration please have a look at the openSAP<\/strong> course from the Further Reference<\/strong> section.<\/p>\nStep 1<\/strong><\/h3>\nOpen API scan in Tosca commander.<\/p>\n
![\"API](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_1-1-1024x387.png\")
<\/a><\/p>\nStep 2<\/strong><\/h3>\nOnce the API scan opens up you can open Int4 IFTT run WSDL file using the File menu and Tosca will prepare an executable SOAP Service call. Over there you can either specify an Int4 IFTT<\/strong> test case ID -ItTestCasesList or a whole test folder – ItScenariosList. Make sure you populate the authentication tab where you need to set authorization for your system where Int4 IFTT is installed (like Solution Manager, S\/4HANA system or a another SAP Netweaver instance).<\/p>\n![\"Tricentis](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_2-1-1024x493.png\")
<\/a><\/p>\nStep 3<\/strong><\/h3>\nNow export your API test into Tosca Commander to finish creating the Test configuration.<\/p>\n
![\"API](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_3-1-1024x350.png\")
<\/a><\/p>\nStep 4<\/strong><\/h3>\nAdd the changeable field – Int4 IFTT test case ID – ItTestCasesList or a whole test folder – ItScenariosList as a variable by using the variable create button.<\/p>\n
![\"RunTests](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure-4-1-1024x579.png\")
<\/a><\/p>\nStep 5<\/strong><\/h3>\nPre-populate the Int4 IFTT test case ID in the in the test case to run the demo.<\/p>\n
![\"Int4](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_5-1-1024x545.png\")
<\/a><\/p>\nStep 6<\/strong><\/h3>\nAdd output and validation variables which we need to check after the run is done. You can use two variables:<\/p>\n
a) EvTCFailed – numer of failed test cases – which should be = 0 if the run is correct
\nb) EvReportURL – url with the results from Int4 IFTT run where you can get detailed information about the run<\/p>\n
![\"output](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_6-1-1024x594.png\")
<\/a><\/p>\nStep 7<\/strong><\/h3>\nIn the test case response you can mark to verify that EvTCFailed = 0 and EvTCFailed is populated as shown in Figure below.<\/p>\n
![\"EvTCFailed](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_7-1-1024x531.png\")
<\/a><\/p>\nStep 8<\/strong><\/h3>\nOnce you finish you can try running the scenario in the scratchbook.<\/p>\n
![\"Run](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_8-1-1024x588.png\")
<\/a><\/p>\nOnce the test is successful you should get the status in the scratchbook.<\/p>\n
![\"ScratchBook\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/Figure_9-1-1024x499.png\")
<\/a><\/p>\nFurther reference:<\/strong><\/h2>\na) Free openSAP course: Virtualize and Automate Your SAP Testing Using Int4 IFTT<\/a><\/p>\n![\"Int4](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/openSAP-1-1024x506.png\")
<\/a><\/p>\nb) Use our openSAP learning paths<\/a> to find the lesson specific to a single testing use case<\/p>\n
- \n
- What SAP API is<\/li>\n
- What does it mean to test the SAP API<\/li>\n
- How to quickly build test cases<\/li>\n
- How to run all test cases from a single platform<\/li>\n
- How to integrate Int4 IFTT with Tricentis Tosca<\/li>\n<\/ul>\n<\/div>\n
\n<\/div>\n
In his latest book “Enterprise Continuous Testing: Transforming Testing for Agile and DevOps” Wolfgang Platz mentions that API testing is the future of automated testing as it is the only part of enterprise system testing where in reality you can automate >85% of test cases.<\/p>\n
<\/p>\n
What is SAP API in reality?<\/strong><\/h2>\n
Most of the companies which use SAP use asynchronous (IDOC, Proxy) integration scenarios for their B2B partners or legacy systems. Most of those message exchanges however are using SAP middleware products like SAP Process Orchestration (SAP PO) or SAP Cloud Platform Integration (SCPI).<\/p>\n
What does it mean to test the SAP API?<\/strong><\/h2>\n
There are many use cases but the most common ones are:<\/p>\n
– SAP Process Orchestration (SAP PO) upgrades, patching or migrations
\n– non SAP middleware to SAP Process Orchestration (SAP PO) migrations
\n– SAP Process Orchestration (SAP PO) to SAP Cloud Platform Integration (SCPI) migrations
\n– continuous testing of SAP Process Orchestration (SAP PO) or SAP Cloud Platform Integration (SCPI) integration flows
\n– SAP Application Interface Framework (SAP AIF) testing
\n– testing IDOC, Proxy scenarios at the S\/4HANA (or any other SAP backend) system<\/p>\nHow can we quickly build test cases for those use cases?<\/strong><\/h2>\n
Int4 IFTT is the only Native SAP certified testing tool which fully supports all of the above use cases out of the box. Due to the nature of asynchronous integration and Int4 IFTT<\/a><\/strong><\/span> prebuild accelerators, test cases for all use case can be implemented in days\/weeks and not in months as with other software which is not designed specifically for SAP API testing.<\/p>\n
More information about testing SAP application integration scenarios can be found in our free openSAP<\/strong> course: Virtualize and Automate Your SAP Testing Using Int4 IFTT<\/a><\/p>\n
Can we use test SAP API with Int4 IFTT from Tricentis Tosca?<\/strong><\/h2>\n
Int4 IFTT is a complementary product to Tricentis Tosca and you can easily run all of your test cases from a single platform (like Tricentis Tosca). In order to do that you can call Int4 IFTT api directly from Tricentis Tosca as shown in the example below and analyse the results of all types of testing in a single tool.<\/p>\n
How can we integrate Int4 IFTT with Tricentis Tosca?<\/strong><\/h2>\n
Below you can find a simplified example on how to run Int4 IFTT from Tricentis Tosca. For Int4 IFTT configuration please have a look at the openSAP<\/strong> course from the Further Reference<\/strong> section.<\/p>\n
Step 1<\/strong><\/h3>\n
Open API scan in Tosca commander.<\/p>\n
<\/a><\/p>\nStep 2<\/strong><\/h3>\n
Once the API scan opens up you can open Int4 IFTT run WSDL file using the File menu and Tosca will prepare an executable SOAP Service call. Over there you can either specify an Int4 IFTT<\/strong> test case ID -ItTestCasesList or a whole test folder – ItScenariosList. Make sure you populate the authentication tab where you need to set authorization for your system where Int4 IFTT is installed (like Solution Manager, S\/4HANA system or a another SAP Netweaver instance).<\/p>\n
<\/a><\/p>\nStep 3<\/strong><\/h3>\n
Now export your API test into Tosca Commander to finish creating the Test configuration.<\/p>\n
<\/a><\/p>\nStep 4<\/strong><\/h3>\n
Add the changeable field – Int4 IFTT test case ID – ItTestCasesList or a whole test folder – ItScenariosList as a variable by using the variable create button.<\/p>\n
<\/a><\/p>\nStep 5<\/strong><\/h3>\n
Pre-populate the Int4 IFTT test case ID in the in the test case to run the demo.<\/p>\n
<\/a><\/p>\nStep 6<\/strong><\/h3>\n
Add output and validation variables which we need to check after the run is done. You can use two variables:<\/p>\n
a) EvTCFailed – numer of failed test cases – which should be = 0 if the run is correct
\nb) EvReportURL – url with the results from Int4 IFTT run where you can get detailed information about the run<\/p>\n<\/a><\/p>\nStep 7<\/strong><\/h3>\n
In the test case response you can mark to verify that EvTCFailed = 0 and EvTCFailed is populated as shown in Figure below.<\/p>\n
<\/a><\/p>\nStep 8<\/strong><\/h3>\n
Once you finish you can try running the scenario in the scratchbook.<\/p>\n
<\/a><\/p>\nOnce the test is successful you should get the status in the scratchbook.<\/p>\n
<\/a><\/p>\nFurther reference:<\/strong><\/h2>\n
a) Free openSAP course: Virtualize and Automate Your SAP Testing Using Int4 IFTT<\/a><\/p>\n
<\/a><\/p>\nb) Use our openSAP learning paths<\/a> to find the lesson specific to a single testing use case<\/p>\n
![\"Int4](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/12\/learning-209x300.png\")
<\/a><\/p>\n