Today we’re going to return to the subject of testing and look at another case study. This time we’re joined by Pieter Atling who recently worked on the SAP PI/PO and webMethods upgrade at AkzoNobel As the test manager Pieter executed several kinds of testing including regression testing. At the beginning of the project, Pieter was asked to find a tool that could handle some automated testing.
At AkzoNobel testing middleware is a huge task as this is for most of the companies. Over the last couple of years many interfaces have been implemented. The company uses SAP PI mainly for application to application A2A interfaces. 500 interfaces are being run over the system. The company needed to implement automated testing in order to better improve the system. Pieter downloaded one of the earliest versions of Figaf’s IRT to implement regression testing.
Besides regression testing with the IRT tooling also end-to-end testing is done to make sure the interface is working as it should work. The expectation is that with the help of the tool upgrades could be done more frequently so that only regression tests have to be done combined with some manual testing done by the technical teams and that the user is not involved or just limited involved. But Pieter thinks as the use of this tool becomes more commonplace there will be more confident in it’s use.
The approach how regression testing is done with IRT, is more or less the same as the approach followed for regression the webMethods platform that is also used by AkzoNobel.
Pieter feels the tool is really useful for fast growing companies who depend on SAP PI for their delivery process. Without a good regression testing tool problems with SAP PI can become a bottleneck. Convincing the development team to use the IRT was fairly easy because of it’s ease of use.
Kishore Nanda is an integration expert who has worked with SAP for many years. In this edition of the podcast, we discuss his experience with SAP PI and Cloud Integrationas well as Dell Boomi and Mulesoft. He has been working on various integration solutions using a variety of platforms. Too often professionals develop myopic focus on SAP without paying attention to other solutions like Boomi and Mulesoft. As a person coming from the SAP ecosystem, it is interesting to hear what is going on in the world outside.
Dell Boomi offers a cloud application that includes interfaces that can be deployed throughout the cloud. The can have instances running on servers that can use in multiple deployment options. Atom Cloud, for example, allows for the same instances running in multiple places which allows for load balancing and offers very high reliability. Boomi also offers predefined content very similar to SAP. My interpretation is that it depends on the supplied APIs and how they work.
Mulesoft have a full integration suite that supports the same things as SAP PI/PO with ESB, API management, and Workflow/BPM. It design approach is different for the integrations.
Kishore says the best reason that an SAP PI user should consider using Boomi or Mulesoft is licensing and how they integrate with a specific system. The key point is that Boomi allows you to deploy an optimized solution for those customers who don’t want to move all of their systems onto the cloud. On the downside, Boomi and Mule have a greater learning curve because of their reliance on more programmatic language.
In this episode, we will talk about SAP PI/PO testing and how to automate it with Figaf IRT.
I’m very happy to have Mark Oshifeso on the show. Mark was one of the first people to use Figaf’s new Integration Regression Tool for SAP PI/PO. Mark works for a mid-size oil and gas producer based in Texas. He and his team upgrade the systems on a regular basis and have found the IRT especially useful on their PI systems.
Mark wanted to make it a lot easier to do upgrades of the SAP PI/PO system. The big challenge was that he used to upgrade the SAP PI/PO system only every 2-3 years because the testing requirement was really big. So the cost was too high it too a long time between upgrades.
“Fully automated testing in the SAP world is pretty rare.” He says.
Mark compares the IRT to other testing options on the market very favorably.
“It’s crazy easy to use.” He added.
The IRT doesn’t require you to learn a programming language and can be taught to someone in as little as an hour. Mark and his team decided to introduce the tool and create a test catalog by upgrading their PI system from one service tech level to a more recent version. They were able to complete their work quite quickly.
One of the big things that I’m grateful Mark helped with is the business side and share how the business could react to automated testing. And then give me the good difference between the normal workflow testing tools and the Record Replay tool.
With the help of Figaf IRT Mark and Anadarko was able to setup a testing of all 300 interfaces in 4 weeks, part of this was the 3 weeks to create the test catalog. Once this is there the overall testing time should go down to 1 week including manual tests. And at the time Figaf where also doing development to enable the recording of the scenarios Mark was using.
You can see the slides here
In the podcast Mark also cover one of the big aspects which are to get business buying of the project. In Anadarko’s case, the business and accounting is responsible for making sure that there is sign off on all interfaces being tested. So each business owner needs to approve the testing result.
The business really enjoyed the testing framework and a lot of their questions was regarding how automated testing worked.
We also cover the two different approaches for testing.
Workflow based in which you define a scenario for testing a message. So you program to place a file here, and then SAP PI will map the file. Next step is then to query the receiving system if everything is correct. Mark estimated that it takes up to 4 hours (when special data etc is required). An interface which doesn’t require any special things can be done in 30min.
The other approach that Figaf IRT user’s is the Record/Replay. Here you simply copy some message from production and run them on your test system. If messages are different then you must evaluate if it is okay or you need to do something with it. Here you don’t have any coding options, but just simple configuration. All of this was enough for Mark and Anadarko to setup the testing.
Mark was using the Rest API of IRT to integrate it with HP ALM which is used to track all testing performed.
If you are looking to do setup any testing of your SAP PI/PO system then have a look at figaf.com/irt. We do have a free plan that will allow you to test 10 interface.