History<\/h2>\r\n<\/span>\r\n\r\n\r\n\r\nSAP has prepared a first version of a SAP PO upgrade testing tool – PIT. It’s being shipped with SP14 to SAP PO which is currently released.\u00a0 The tool perfectly complements Int4 IFTT<\/a> testing tool in one scenario the so please have a look how you can configure it to help you perform an SAP PO upgrade more easily. \u00a0\u00a0<\/p>\r\n<\/div>\r\n\r\n\r\n\r\n
Use cases <\/strong><\/h3>\r\n\r\n\r\n\r\nSAP Test Tool primarily focuses:<\/p>\r\n\r\n\r\n\r\n
\r\n- help with SAP PO dual stack (ABAP & JAVA) to single stack migrations (JAVA only)<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
<\/p>\r\n\r\n\r\n\r\n
Availability\/prerequisites <\/strong><\/h3>\r\n\r\n\r\n\r\nIn order to use SAP Test Tool you need to have SAP PO 7.5 SP14 (where you can install it or run test scenarios) but if you just want to feed the SAP Test Tool with data you can use a system from 7.31 SP17 or 7.5 SP06 or higher.<\/p>\r\n\r\n\r\n\r\n
For each message used as a source you need to enable logging on BI, MS, AM.<\/p>\r\n\r\n\r\n\r\n
Current limitations (this may be subject to change)<\/p>\r\n
\n- ICOs with sender\/receiver wild cards<\/li>\n
- Sync\/async, async\/sync bridges<\/li>\n
- Mapping splits<\/li>\n
- Flows with Decentralized adapter engines<\/li>\n
- No adapter modules are tested<\/li>\n<\/ul>\n<\/div>\r\n\r\n\r\n\r\n\r\n\r\n
Terminology used in SAP Test Tool<\/strong><\/h2>\r\n\r\n\r\n\r\nTest system<\/strong><\/span> – SAP PO system in the landscape which is used for testing – either as source (feeding the Test tool with messages) , target (where sender’s messages are executed) – those are used in dual stack to single stack migrations or both (sender and target) which is a typical use case for regression testing on a single system.<\/p>\r\n\r\n\r\n\r\nTest Case<\/strong><\/span> – SAP PO routing configuration which is being tested (ICO, etc.)<\/p>\r\n\r\n\r\n\r\nTest Data Set<\/strong><\/span> – a set of messages (successfully processed) which is a subject for testing.<\/p>\r\n\r\n\r\n\r\nRun configuration<\/strong><\/span> – specifies on which landscape should the test case be executed<\/p>\r\n\r\n\r\n\r\nAuthorizations<\/strong><\/h3>\r\n\r\n\r\n\r\nIn order to be able to create the configuration and run it you’d need the following roles: SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR.<\/p>\r\n\r\n\r\n\r\n
Configuration <\/strong><\/h3>\r\n\r\n\r\n\r\nCurrently SAP Test Tool is using NWDS as a main configuration tool. The scenario below will describe how to do regression testing on a single SAP PO system. We will find a successfully processed message, do a mapping change and see what will happen once we reprocess the same message via the same ICO. Ideally it should display all of the differencies between the two runs.<\/p>\r\n\r\n\r\n\r\n
Step 1 <\/strong><\/h4>\r\n\r\n\r\n\r\nOpen NWDS and find the new perspective: SAP Process Integration Test.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_1.png\")
<\/figure>\r\n\r\n\r\n\r\nStep 2<\/strong><\/h4>\r\n\r\n\r\n\r\nOpen preferences and insert connection data to your SAP PO were the SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_2.png\")
<\/figure>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_3-1024x616.png\")
<\/figure>\r\n\r\n\r\n\r\nStep 3 <\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step you need to define the systems (source and target) where you need to run your tests. In this case it’s the same system where SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_4-1024x193.png\")
<\/figure>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_5-1024x718.png\")
<\/figure>\r\n\r\n\r\n\r\nStep 4 <\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step we can start creating Test Cases.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_6-1024x220.png\")
<\/figure>\r\n\r\n\r\n\r\nSelect the type of the flow you want to test.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_7-1024x971.png\")
<\/figure>\r\n\r\n\r\n\r\nIn the next step it’s time to select the routing object itself (ICO).<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_8-1-1024x969.png\")
<\/figure>\r\n\r\n\r\n\r\nStep 5<\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step the Test case is created so we can populate it with test data. In order to do that select the Test Data tab of the Test Case.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_9.png\")
<\/figure>\r\n\r\n\r\n\r\nThen select the “Add” button to add messages to the test data where you can specify the source system from which you want to fetch the data.<\/p>\r\n\r\n\r\n\r\n
Next select the time range when the message was created and the message itself.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_11-1024x491.png\")
<\/figure>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_12-1024x326.png\")
<\/figure>\r\n\r\n\r\n\r\nOn the Verification tab of the Test case you can also define which parts of the message should not be checked (dates, etc.).<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_13.png\")
<\/figure>\r\n\r\n\r\n\r\nThis step finishes the configuration\/customizing part of the SAP Test Tool.<\/p>\r\n\r\n\r\n\r\n
Run and validation<\/strong><\/h2>\r\n\r\n\r\n\r\nIn order to run the test you need to create a new run configuration.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_14.png\")
<\/figure>\r\n\r\n\r\n\r\nWhere you need to specify the Test Case and the landscape of the execution.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_15.png\")
<\/figure>\r\n\r\n\r\n\r\nWhat you can also select here is the checkbox “Stop message before delivering to Receiver” which will automatically cancel the Test message after processing so it will not overload the receiver system.<\/p>\r\n\r\n\r\n\r\n
Once you press Run the Test Case will get executed and the TestRun is executed you can send it for Verification which will compare the old (original) target message with the new one created by executing the Test Case.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_16.png\")
<\/figure>\r\n\r\n\r\n\r\nAs I’ve changed the mapping before running the Test Case what we can see is that there are some differences found.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_17.png\")
<\/figure>\r\n\r\n\r\n\r\nIn the Error Overview section we can see a more detailed description talling us the what is different between the original message and the one from the Test Run.<\/p>\r\n\r\n\r\n\r\n![\"\"](\"https:\/\/www.int4.com\/wp-content\/uploads\/2019\/03\/Figure_18.png\")
<\/figure>\r\n\r\n\r\n\r\n
<\/div>\r\n\r\n\r\n\r\n
Use cases <\/strong><\/h3>\r\n\r\n\r\n\r\nSAP Test Tool primarily focuses:<\/p>\r\n\r\n\r\n\r\n
\r\n- help with SAP PO dual stack (ABAP & JAVA) to single stack migrations (JAVA only)<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n
<\/p>\r\n\r\n\r\n\r\n
Availability\/prerequisites <\/strong><\/h3>\r\n\r\n\r\n\r\nIn order to use SAP Test Tool you need to have SAP PO 7.5 SP14 (where you can install it or run test scenarios) but if you just want to feed the SAP Test Tool with data you can use a system from 7.31 SP17 or 7.5 SP06 or higher.<\/p>\r\n\r\n\r\n\r\n
For each message used as a source you need to enable logging on BI, MS, AM.<\/p>\r\n\r\n\r\n\r\n
Current limitations (this may be subject to change)<\/p>\r\n
\n- ICOs with sender\/receiver wild cards<\/li>\n
- Sync\/async, async\/sync bridges<\/li>\n
- Mapping splits<\/li>\n
- Flows with Decentralized adapter engines<\/li>\n
- No adapter modules are tested<\/li>\n<\/ul>\n<\/div>\r\n\r\n\r\n\r\n\r\n\r\n
Terminology used in SAP Test Tool<\/strong><\/h2>\r\n\r\n\r\n\r\nTest system<\/strong><\/span> – SAP PO system in the landscape which is used for testing – either as source (feeding the Test tool with messages) , target (where sender’s messages are executed) – those are used in dual stack to single stack migrations or both (sender and target) which is a typical use case for regression testing on a single system.<\/p>\r\n\r\n\r\n\r\nTest Case<\/strong><\/span> – SAP PO routing configuration which is being tested (ICO, etc.)<\/p>\r\n\r\n\r\n\r\nTest Data Set<\/strong><\/span> – a set of messages (successfully processed) which is a subject for testing.<\/p>\r\n\r\n\r\n\r\nRun configuration<\/strong><\/span> – specifies on which landscape should the test case be executed<\/p>\r\n\r\n\r\n\r\nAuthorizations<\/strong><\/h3>\r\n\r\n\r\n\r\nIn order to be able to create the configuration and run it you’d need the following roles: SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR.<\/p>\r\n\r\n\r\n\r\n
Configuration <\/strong><\/h3>\r\n\r\n\r\n\r\nCurrently SAP Test Tool is using NWDS as a main configuration tool. The scenario below will describe how to do regression testing on a single SAP PO system. We will find a successfully processed message, do a mapping change and see what will happen once we reprocess the same message via the same ICO. Ideally it should display all of the differencies between the two runs.<\/p>\r\n\r\n\r\n\r\n
Step 1 <\/strong><\/h4>\r\n\r\n\r\n\r\nOpen NWDS and find the new perspective: SAP Process Integration Test.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 2<\/strong><\/h4>\r\n\r\n\r\n\r\nOpen preferences and insert connection data to your SAP PO were the SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 3 <\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step you need to define the systems (source and target) where you need to run your tests. In this case it’s the same system where SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 4 <\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step we can start creating Test Cases.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nSelect the type of the flow you want to test.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nIn the next step it’s time to select the routing object itself (ICO).<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 5<\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step the Test case is created so we can populate it with test data. In order to do that select the Test Data tab of the Test Case.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nThen select the “Add” button to add messages to the test data where you can specify the source system from which you want to fetch the data.<\/p>\r\n\r\n\r\n\r\n
Next select the time range when the message was created and the message itself.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nOn the Verification tab of the Test case you can also define which parts of the message should not be checked (dates, etc.).<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nThis step finishes the configuration\/customizing part of the SAP Test Tool.<\/p>\r\n\r\n\r\n\r\n
Run and validation<\/strong><\/h2>\r\n\r\n\r\n\r\nIn order to run the test you need to create a new run configuration.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nWhere you need to specify the Test Case and the landscape of the execution.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nWhat you can also select here is the checkbox “Stop message before delivering to Receiver” which will automatically cancel the Test message after processing so it will not overload the receiver system.<\/p>\r\n\r\n\r\n\r\n
Once you press Run the Test Case will get executed and the TestRun is executed you can send it for Verification which will compare the old (original) target message with the new one created by executing the Test Case.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nAs I’ve changed the mapping before running the Test Case what we can see is that there are some differences found.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nIn the Error Overview section we can see a more detailed description talling us the what is different between the original message and the one from the Test Run.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n
<\/p>\r\n\r\n\r\n\r\n
Availability\/prerequisites <\/strong><\/h3>\r\n\r\n\r\n\r\nIn order to use SAP Test Tool you need to have SAP PO 7.5 SP14 (where you can install it or run test scenarios) but if you just want to feed the SAP Test Tool with data you can use a system from 7.31 SP17 or 7.5 SP06 or higher.<\/p>\r\n\r\n\r\n\r\n
For each message used as a source you need to enable logging on BI, MS, AM.<\/p>\r\n\r\n\r\n\r\n
Current limitations (this may be subject to change)<\/p>\r\n
\n- ICOs with sender\/receiver wild cards<\/li>\n
- Sync\/async, async\/sync bridges<\/li>\n
- Mapping splits<\/li>\n
- Flows with Decentralized adapter engines<\/li>\n
- No adapter modules are tested<\/li>\n<\/ul>\n<\/div>\r\n\r\n\r\n\r\n\r\n\r\n
Terminology used in SAP Test Tool<\/strong><\/h2>\r\n\r\n\r\n\r\nTest system<\/strong><\/span> – SAP PO system in the landscape which is used for testing – either as source (feeding the Test tool with messages) , target (where sender’s messages are executed) – those are used in dual stack to single stack migrations or both (sender and target) which is a typical use case for regression testing on a single system.<\/p>\r\n\r\n\r\n\r\nTest Case<\/strong><\/span> – SAP PO routing configuration which is being tested (ICO, etc.)<\/p>\r\n\r\n\r\n\r\nTest Data Set<\/strong><\/span> – a set of messages (successfully processed) which is a subject for testing.<\/p>\r\n\r\n\r\n\r\nRun configuration<\/strong><\/span> – specifies on which landscape should the test case be executed<\/p>\r\n\r\n\r\n\r\nAuthorizations<\/strong><\/h3>\r\n\r\n\r\n\r\nIn order to be able to create the configuration and run it you’d need the following roles: SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR.<\/p>\r\n\r\n\r\n\r\n
Configuration <\/strong><\/h3>\r\n\r\n\r\n\r\nCurrently SAP Test Tool is using NWDS as a main configuration tool. The scenario below will describe how to do regression testing on a single SAP PO system. We will find a successfully processed message, do a mapping change and see what will happen once we reprocess the same message via the same ICO. Ideally it should display all of the differencies between the two runs.<\/p>\r\n\r\n\r\n\r\n
Step 1 <\/strong><\/h4>\r\n\r\n\r\n\r\nOpen NWDS and find the new perspective: SAP Process Integration Test.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 2<\/strong><\/h4>\r\n\r\n\r\n\r\nOpen preferences and insert connection data to your SAP PO were the SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 3 <\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step you need to define the systems (source and target) where you need to run your tests. In this case it’s the same system where SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 4 <\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step we can start creating Test Cases.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nSelect the type of the flow you want to test.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nIn the next step it’s time to select the routing object itself (ICO).<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 5<\/strong><\/h4>\r\n\r\n\r\n\r\nIn the next step the Test case is created so we can populate it with test data. In order to do that select the Test Data tab of the Test Case.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nThen select the “Add” button to add messages to the test data where you can specify the source system from which you want to fetch the data.<\/p>\r\n\r\n\r\n\r\n
Next select the time range when the message was created and the message itself.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nOn the Verification tab of the Test case you can also define which parts of the message should not be checked (dates, etc.).<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nThis step finishes the configuration\/customizing part of the SAP Test Tool.<\/p>\r\n\r\n\r\n\r\n
Run and validation<\/strong><\/h2>\r\n\r\n\r\n\r\nIn order to run the test you need to create a new run configuration.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nWhere you need to specify the Test Case and the landscape of the execution.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nWhat you can also select here is the checkbox “Stop message before delivering to Receiver” which will automatically cancel the Test message after processing so it will not overload the receiver system.<\/p>\r\n\r\n\r\n\r\n
Once you press Run the Test Case will get executed and the TestRun is executed you can send it for Verification which will compare the old (original) target message with the new one created by executing the Test Case.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nAs I’ve changed the mapping before running the Test Case what we can see is that there are some differences found.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nIn the Error Overview section we can see a more detailed description talling us the what is different between the original message and the one from the Test Run.<\/p>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\n
- \n
- ICOs with sender\/receiver wild cards<\/li>\n
- Sync\/async, async\/sync bridges<\/li>\n
- Mapping splits<\/li>\n
- Flows with Decentralized adapter engines<\/li>\n
- No adapter modules are tested<\/li>\n<\/ul>\n<\/div>\r\n\r\n\r\n\r\n\r\n\r\n
Terminology used in SAP Test Tool<\/strong><\/h2>\r\n\r\n\r\n\r\n
Test system<\/strong><\/span> – SAP PO system in the landscape which is used for testing – either as source (feeding the Test tool with messages) , target (where sender’s messages are executed) – those are used in dual stack to single stack migrations or both (sender and target) which is a typical use case for regression testing on a single system.<\/p>\r\n\r\n\r\n\r\n
Test Case<\/strong><\/span> – SAP PO routing configuration which is being tested (ICO, etc.)<\/p>\r\n\r\n\r\n\r\n
Test Data Set<\/strong><\/span> – a set of messages (successfully processed) which is a subject for testing.<\/p>\r\n\r\n\r\n\r\n
Run configuration<\/strong><\/span> – specifies on which landscape should the test case be executed<\/p>\r\n\r\n\r\n\r\n
Authorizations<\/strong><\/h3>\r\n\r\n\r\n\r\n
In order to be able to create the configuration and run it you’d need the following roles: SAP_PIT_TEST_DEVELOPER, SAP_PIT_LANDSCAPE_ADMINISTRATOR.<\/p>\r\n\r\n\r\n\r\n
Configuration <\/strong><\/h3>\r\n\r\n\r\n\r\n
Currently SAP Test Tool is using NWDS as a main configuration tool. The scenario below will describe how to do regression testing on a single SAP PO system. We will find a successfully processed message, do a mapping change and see what will happen once we reprocess the same message via the same ICO. Ideally it should display all of the differencies between the two runs.<\/p>\r\n\r\n\r\n\r\n
Step 1 <\/strong><\/h4>\r\n\r\n\r\n\r\n
Open NWDS and find the new perspective: SAP Process Integration Test.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nStep 2<\/strong><\/h4>\r\n\r\n\r\n\r\n
Open preferences and insert connection data to your SAP PO were the SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 3 <\/strong><\/h4>\r\n\r\n\r\n\r\n
In the next step you need to define the systems (source and target) where you need to run your tests. In this case it’s the same system where SAP Test Tool is installed.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nStep 4 <\/strong><\/h4>\r\n\r\n\r\n\r\n
In the next step we can start creating Test Cases.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nSelect the type of the flow you want to test.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nIn the next step it’s time to select the routing object itself (ICO).<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nStep 5<\/strong><\/h4>\r\n\r\n\r\n\r\n
In the next step the Test case is created so we can populate it with test data. In order to do that select the Test Data tab of the Test Case.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nThen select the “Add” button to add messages to the test data where you can specify the source system from which you want to fetch the data.<\/p>\r\n\r\n\r\n\r\n
Next select the time range when the message was created and the message itself.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\n<\/figure>\r\n\r\n\r\n\r\nOn the Verification tab of the Test case you can also define which parts of the message should not be checked (dates, etc.).<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nThis step finishes the configuration\/customizing part of the SAP Test Tool.<\/p>\r\n\r\n\r\n\r\n
Run and validation<\/strong><\/h2>\r\n\r\n\r\n\r\n
In order to run the test you need to create a new run configuration.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nWhere you need to specify the Test Case and the landscape of the execution.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nWhat you can also select here is the checkbox “Stop message before delivering to Receiver” which will automatically cancel the Test message after processing so it will not overload the receiver system.<\/p>\r\n\r\n\r\n\r\n
Once you press Run the Test Case will get executed and the TestRun is executed you can send it for Verification which will compare the old (original) target message with the new one created by executing the Test Case.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nAs I’ve changed the mapping before running the Test Case what we can see is that there are some differences found.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\nIn the Error Overview section we can see a more detailed description talling us the what is different between the original message and the one from the Test Run.<\/p>\r\n\r\n\r\n\r\n
<\/figure>\r\n\r\n\r\n\r\n