In this article you will learn:<\/h2>\n\n- How Int4 IFTT can use external tools to automate manual steps required to test business scenarios<\/li>\n
- How to combine Int4 IFTT API Testing<\/a> and SAP CBTA to test S\/4HANA Scenarios involving Fiori apps<\/li>\n<\/ul>\n<\/div>\n
Reading time: 6 minutes<\/span><\/strong><\/p>\n\n<\/div>\n
Introduction<\/h3>\n
As companies are migrating their ERP landscapes to the latest SAP S\/4HANA<\/a> solution, solutions allowing for minimization of business involvement and timeline reduction gain traction. Such migration projects<\/a> are often complex and challenging in many dimensions, testing being one that is often overlooked. Int4 IFTT can support such projects by providing a cost efficient way to validate that the new solution performs as expected and integrations scenarios (B2B-EDI, integration with internal non- SAP systems, etc.) are still working.<\/p>\nWith S\/4HANA implementation many companies are reviewing their User Experience strategy and implementing SAP Fiori as the main user interface for accessing the system. What does it mean for testing the end-to-end integration processes? Some of the manual actions are executed now in the web environment and no longer in SAP GUI. In this article, we will show how Int4 IFTT can leverage other testing tools like SAP Component Based Test Automation (CBTA) to automate manual steps<\/a> in Fiori applications and provide test coverage for complex integrated business processes.<\/p>\nIt?s a good time to refresh how Int4 IFTT integrates with SAP Solution Manager Test Suite<\/a> by using Composite Tests, where Test Suite is the primary testing solution in your landscape used to manage, execute test cases and analyze test results. Int4 IFTT can be as well the leading system and integration Test Suite scripts in the Int4 IFTT test scenarios. We will use this approach going forward.<\/p>\nHere is the outline of the Business process to be automated:<\/p>\n
\n- Purchase Order created with S\/4HANA application Manage Purchase Orders<\/li>\n
- Inbound Delivery XML message sent from external system to SAP Process Orchestration<\/li>\n
- XML message transformed by SAP Process Orchestration to IDOC and posted in S\/4HANA
\n<\/div><\/li>\n<\/ul>\n![\"S\/4HANA_Fiori\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/Tomek-illustr.png\")
<\/a><\/p>\nPrerequisites<\/h3>\n\n- Int4 IFTT installed on Solution Manager 7.2<\/li>\n
- SAP Solution Manager Configuration for CBTA completed (https:\/\/bit.ly\/3qcOSA2)<\/li>\n
- CBTA Client Installed locally (installation details: https:\/\/bit.ly\/383cwc4)<\/li>\n
- Int4 IFTT landscape with S\/4HANA system configured
\n<\/div><\/li>\n<\/ul>\nStep-by-step<\/h3>\n1. Go to Solution Manage Launchpad<\/h6>\n2. Open Test Repository Tile<\/h6>\n
![\"Test_repository\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/1.png\")
<\/a><\/p>\n
\n3. Create new script selecting CBTA as Test Tool<\/h6>\n
![\"New_test_script\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/2.png\")
<\/a><\/p>\n
\n4. Assign Executable selecting target application<\/h6>\n
![\"Assign_executable\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/3.png\")
<\/a><\/p>\n
\n5. Click Launch CBTA<\/h6>\n
![\"Launch_CBTA\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/4.png\")
<\/a><\/p>\nLocal CBTA Client should be opened which will start web browser with recording feature enabled.<\/p>\n
![\"Test_creation_Wizard\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/5.png\")
<\/a><\/p>\n
\nRecord your UI steps and finalize the script.<\/p>\n
![\"New_purchase_order\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/6.png\")
<\/a><\/p>\n![\"Test_creation_Wizard_report\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/7.png\")
<\/a><\/p>\n
\n6. After transferring the recorded steps to Test Repository go to Test Script Steps and expose Purchase Order number as Export parameter<\/h6>\n
![\"Test_script\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/8.png\")
<\/a><\/p>\n
\n7. You can verify if the UI script was recorded and configured correctly by executing it directly from Test Repository<\/h6>\n
Test result should indicate “Success” and export parameter PURCHASE_ORDER should contain number of created Order.<\/p>\n
![\"Test_script_CBTA\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/9.png\")
<\/a><\/p>\n8. Go to Int4 IFTT Test Cockpit<\/h6>\n9. Create new test case for Purchase Order creation part<\/h6>\n
a. Interface Type = “Test Suite CBTA”<\/p>\n
b. Document number = Name of the script created in step 3<\/p>\n
c. Automation Object = Create a new one or use an existing object. Ensure there is a variable defined for Purchase Order number<\/p>\n
![\"Display_view_Variable_Processing\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/10.png\")
<\/a><\/p>\n![\"Int4_IFTT_Display_Mode\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/11.png\")
<\/a><\/p>\n10. Create new Test Case for Inbound Delivery part<\/h6>\n
a. Interface Type = “PI GUID E2E Inbound”<\/span><\/p>\nb. Document Number = Number of existing message from SAP PI\/PO<\/a>. This can be entered manually or searched using <\/span>Message Selector<\/span><\/a><\/p>\nc. Automation Object = Create a new one or use an existing object for this interface. Ensure there is a variable defined for Purchase Order which will replace the value with the new Order number created in CBTA step<\/span><\/p>\n![\"Display_view_Variable_processing\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/12.png\")
<\/a><\/p>\n
\nd. Parent Id = Test Case Id from step 9<\/span><\/p>\n![\"Int4_IFTT_Display_mode_test_cockpit\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/13.png\")
<\/a><\/p>\n
\n11. Execute the scenario<\/h6>\n
Int4 IFTT will run CBTA script first and then use the created purchase order to trigger Delivery message in SAP PO. Finally IDOC structure and Inbound delivery data are validated with a reference set.<\/p>\n
![\"Int4_IFTT_Test_execution_report\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/14.png\")
<\/a><\/p>\n![\"Int4_IFTT_Test_results_report\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/15.png\")
<\/a><\/p>\n![\"SAP_Backend_documentation_validation\"](\"https:\/\/int4.com\/wp-content\/uploads\/2021\/03\/17.png\")
<\/a><\/p>\nSummary<\/h2>\n
The number of business processes driven from external systems grows. Whether that is EDI, Online stores or integration of internal systems, facing the shift from manual operations to integrated business flow without updating your testing toolkit might be a limiting factor.<\/p>\n
As presented, Int4 IFTT both allows you to test the integration processes directly, and also test the integrated scenario end-to-end by calling your existing user interface testing tools<\/a> to support full process execution.<\/p>\nIn this example we called the existing SAP Test Suite solution and Int4 IFTT can also call other user interface testing tools on the market. In case you do not wish to invest in additional testing solutions to test your business interfaces, Int4 IFTT can call SAP Test Suite (CBTA), which is available within installation of SAP Solution Manager<\/a>.<\/p>\n <\/p>\n
Read also:<\/h4>\n
- \n
- How Int4 IFTT can use external tools to automate manual steps required to test business scenarios<\/li>\n
- How to combine Int4 IFTT API Testing<\/a> and SAP CBTA to test S\/4HANA Scenarios involving Fiori apps<\/li>\n<\/ul>\n<\/div>\n
Reading time: 6 minutes<\/span><\/strong><\/p>\n
\n<\/div>\n
Introduction<\/h3>\n
As companies are migrating their ERP landscapes to the latest SAP S\/4HANA<\/a> solution, solutions allowing for minimization of business involvement and timeline reduction gain traction. Such migration projects<\/a> are often complex and challenging in many dimensions, testing being one that is often overlooked. Int4 IFTT can support such projects by providing a cost efficient way to validate that the new solution performs as expected and integrations scenarios (B2B-EDI, integration with internal non- SAP systems, etc.) are still working.<\/p>\n
With S\/4HANA implementation many companies are reviewing their User Experience strategy and implementing SAP Fiori as the main user interface for accessing the system. What does it mean for testing the end-to-end integration processes? Some of the manual actions are executed now in the web environment and no longer in SAP GUI. In this article, we will show how Int4 IFTT can leverage other testing tools like SAP Component Based Test Automation (CBTA) to automate manual steps<\/a> in Fiori applications and provide test coverage for complex integrated business processes.<\/p>\n
It?s a good time to refresh how Int4 IFTT integrates with SAP Solution Manager Test Suite<\/a> by using Composite Tests, where Test Suite is the primary testing solution in your landscape used to manage, execute test cases and analyze test results. Int4 IFTT can be as well the leading system and integration Test Suite scripts in the Int4 IFTT test scenarios. We will use this approach going forward.<\/p>\n
Here is the outline of the Business process to be automated:<\/p>\n
- \n
- Purchase Order created with S\/4HANA application Manage Purchase Orders<\/li>\n
- Inbound Delivery XML message sent from external system to SAP Process Orchestration<\/li>\n
- XML message transformed by SAP Process Orchestration to IDOC and posted in S\/4HANA
\n<\/div><\/li>\n<\/ul>\n<\/a><\/p>\nPrerequisites<\/h3>\n
- \n
- Int4 IFTT installed on Solution Manager 7.2<\/li>\n
- SAP Solution Manager Configuration for CBTA completed (https:\/\/bit.ly\/3qcOSA2)<\/li>\n
- CBTA Client Installed locally (installation details: https:\/\/bit.ly\/383cwc4)<\/li>\n
- Int4 IFTT landscape with S\/4HANA system configured
\n<\/div><\/li>\n<\/ul>\nStep-by-step<\/h3>\n
1. Go to Solution Manage Launchpad<\/h6>\n
2. Open Test Repository Tile<\/h6>\n
<\/a><\/p>\n
\n3. Create new script selecting CBTA as Test Tool<\/h6>\n
<\/a><\/p>\n
\n4. Assign Executable selecting target application<\/h6>\n
<\/a><\/p>\n
\n5. Click Launch CBTA<\/h6>\n
<\/a><\/p>\nLocal CBTA Client should be opened which will start web browser with recording feature enabled.<\/p>\n
<\/a><\/p>\n
\nRecord your UI steps and finalize the script.<\/p>\n
<\/a><\/p>\n<\/a><\/p>\n
\n6. After transferring the recorded steps to Test Repository go to Test Script Steps and expose Purchase Order number as Export parameter<\/h6>\n
<\/a><\/p>\n
\n7. You can verify if the UI script was recorded and configured correctly by executing it directly from Test Repository<\/h6>\n
Test result should indicate “Success” and export parameter PURCHASE_ORDER should contain number of created Order.<\/p>\n
<\/a><\/p>\n8. Go to Int4 IFTT Test Cockpit<\/h6>\n
9. Create new test case for Purchase Order creation part<\/h6>\n
a. Interface Type = “Test Suite CBTA”<\/p>\n
b. Document number = Name of the script created in step 3<\/p>\n
c. Automation Object = Create a new one or use an existing object. Ensure there is a variable defined for Purchase Order number<\/p>\n
<\/a><\/p>\n<\/a><\/p>\n10. Create new Test Case for Inbound Delivery part<\/h6>\n
a. Interface Type = “PI GUID E2E Inbound”<\/span><\/p>\n
b. Document Number = Number of existing message from SAP PI\/PO<\/a>. This can be entered manually or searched using <\/span>Message Selector<\/span><\/a><\/p>\n
c. Automation Object = Create a new one or use an existing object for this interface. Ensure there is a variable defined for Purchase Order which will replace the value with the new Order number created in CBTA step<\/span><\/p>\n
<\/a><\/p>\n
\nd. Parent Id = Test Case Id from step 9<\/span><\/p>\n
<\/a><\/p>\n
\n11. Execute the scenario<\/h6>\n
Int4 IFTT will run CBTA script first and then use the created purchase order to trigger Delivery message in SAP PO. Finally IDOC structure and Inbound delivery data are validated with a reference set.<\/p>\n
<\/a><\/p>\n<\/a><\/p>\n<\/a><\/p>\nSummary<\/h2>\n
The number of business processes driven from external systems grows. Whether that is EDI, Online stores or integration of internal systems, facing the shift from manual operations to integrated business flow without updating your testing toolkit might be a limiting factor.<\/p>\n
As presented, Int4 IFTT both allows you to test the integration processes directly, and also test the integrated scenario end-to-end by calling your existing user interface testing tools<\/a> to support full process execution.<\/p>\n
In this example we called the existing SAP Test Suite solution and Int4 IFTT can also call other user interface testing tools on the market. In case you do not wish to invest in additional testing solutions to test your business interfaces, Int4 IFTT can call SAP Test Suite (CBTA), which is available within installation of SAP Solution Manager<\/a>.<\/p>\n
<\/p>\n
Read also:<\/h4>\n