Yesterday we released IRT 2.2 to make testing even easier. This release contains a lot of new functionality that makes it a lot easier to test your system.
One of our visions is to make an all round change management tool that allows you to find errors, fix them, document the changes, and test it. We have added the first part of this which is to support the change management, this will allow you to document what is going on in the landscape. So now we have a link from ICO all the way to message mapping. This will allow us to ensure that you test the interfaces before you make any release.
You can see the video for a presentation here.
Watch on YouTube IRT 22 release note how to test SAP PI/PO better
Cloud Integration. We have now added the option to start testing SAP Cloud Integration (CPI aka HCI). It is made possible by the new option to trace information so we don’t need to make modifications to your iflows to test it. We can do a regression test with the HTTP adapter now. For other messages, you need to use the baseline testing, where you will be sending the same message again.
Baseline test cases. This is to make integration with workflow tools like HPE UFT that already create a number of messages to the SAP PI/PO system. So instead of IRT sending test messages the sending system is creating the messages. The test would then compare that the same messages are sent and compare that they are processed in the same order. This is also a function we are using when testing with SAP Cloud Integration.
Change Tracking Tool. In the change tracking tool we have added the ability to see all repository objects and what is changed. So you can see where in an object it changed. The cool thing is that you now can see where a message mapping is used and in which ICO/iFlows it is used. This will give users the option to run test report that covers the things that have been changed.
If you are ready to start testing your SAP PI/PO/CPI solutions better, have a look at the Figaf DevOps Suite.
