Posts

Catch 22 for testing now fixed. Supporting test on all SAP PI/PO systems 7.31+

We got trapped in a Catch 22

We need a feature released 1½ year ago to be able to test SAP PI/PO system, without installing our modules. To upgrade customers need to test their system, but they will have to do the test manually. It would save them a lot of time to use our tool.

We can test the systems if they install one of our components, but it is not something all customers that can install non-SAP components on their PI system. That was the reason we were looking for alternatives. And to make it a lot easier to get to use our tool.

We found the web service was able to give us the payloads of the logs. We got the solution working on our development. When we tried to test it on the older PI system the web service method we wanted was not there. After some digging, we found the solution was released with a patch 1½ years ago. So we could not assist in upgrading without them having to install our component. 

I want to help the customers to use our tool, especially if they have not patched for 1½ year, so they can test better. Then it makes even more sense to test.

This is the screen we web scraping to get message payload

So now we have made an option to use a WebDynpro agent that is able to connect to the screen users are seen and downloading the messages. It will use this if the web service method for downloading content is not available. It is by no means the best solution but it is a way to solve a pressing issue.

The way we did it was to use the Chrome Developer tool to see the different request required to select the correct line, switch the tabs to the payload page and then download the message. Then find the output message and download it. There is a number of requests to view each different page, and we even had to scroll table of payload to view it all.

Check out the video on the topic.

 

If you want to try it out on your own system check http://figaf.com/irt . We even have free version so you can use it to test your systems from your laptop.

Other features added

We have been moving some functionality making the application run faster when you activate new recordings of test cases. So it should start a lot faster.

We have also been improving the functionality to recording/testing or bridges async/sync and sync/async for the Figaf IRT modules. We are also adding the function later to use the SAP logging module.

Whitepaper of what Figaf IRT can do for your SAP PI/PO or CPI integrations

Over the last 6 months, our IRT application has expanded from just being an application that facilitates SAP PI/PO testing to deal with more of the full development process for SAP Integration.  We have added the following capabilities.

  • Filter your SAP PI/PO alerts so you can see new errors and document how old errors can be resolved
  • Enable you to test SAP Cloud Platform Integration(CPI)
  • That you don’t need to install anything at the PI system to use the tool
  • Enable you to track all development objects on SAP PI/PO and CPI so you can see the difference on each one
  • Create Ticket to log which objects you have changed for any specific use cases, so you can document what you have done to solve a ticket.

    Download the Figaf IRT white paper now

    • Test all the ICOs where an object is used like a message mapping

We have had some challenging trying to communicate all of the functions that we are supporting in the process and how it worked. So now I finally was able to create a document that tries to explain all the capabilities we have in an easy to read manner.

We have tried to make it as appealing to the business but also explain what we are doing to make the life easier for integration developers.

You can download it here

If you have any idea on how to improve it, please share.

Get FIGAF IRT and start using it for free here

 

 

 

Why have a full SAP PI/PO regression test case is needed

Do you have a full set of regression test cases of your SAP PI/PO system and can run them when needed to ensure that nothing is broken.

This week I was talking with a potential customer about our testing tool and the newest feature where they did not need to install anything on the PI system. They did, unfortunately, have a too old version of one of the components to allow us to read the log messages. It was added with OSS 2437778.

It is the standard way out to add new features to patches or service packs to give customers there the features which are required. Most of all the time you want to be able to leverage the new functions in some scenarios to solve a business need.

With the way SAP is delivering the Java code is it cumulative patches. This mean that patch 3 contains updates from patch 2 plus some more changes. So you cannot just get the fix you want as you can with ABAP.

They are also linked with dependencies so if you upgrade one, some part will stop function because it is missing a dependent library. So most of the time you have to update quite a bit of component and you have no idea about how this will affect everything else. You can read the release notes, but it is difficult or close to impossible to predict how this will impact your system.

And to make matters even worse, you probably need to upgrade all components to the latest to ensure all dependencies are met.  

In a normal company it will take a long time to validate these things, so if you’re just adding a simple feature it is really a no go to do this. The business case is difficult to explain, we want this feature to do X, but it will cost a lot of testing. So you have to wait for the business to ask for a new feature and then that project would have to pay for the upgrade/patch.

That’s the reason why I want to have a full set of regression test cases that you can just run whenever there is any patch or an upgrade that you have to ensure that everything works as expected without involving people in the testing of the new features.

The price for an upgrade is a partial basis to get them to upgrade the system and then a part to test the component. The biggest cost is the tests that you need to perform to ensure that everything works as expected. It makes, therefore, sense that to be able to automate that part if it is possible.

With most test tools that take a long time to set up these the test cases and that’s why we’ve created a tool to enable you to set up these test cases fast.  We had a customer Anadarko Petroleum Corporation that could set up 300 test cases in just 3 weeks.

Since then we have optimized the process a lot making it a lot faster to set up test cases. So I would assume you will be able to set up test cases a lot faster than now.

The cost of running the test for the full system is close to zero, so you can run them daily to get information about how the system performs or if anything is broken.

So you can apply the latest support packs if you want to have an updated system with the latest features and fixes.

You can download Figaf IRT tool and use the tool for free upto 10 ICO’s to test on your own SAP PI/PO system. You can request a trial license to get more tests done. If you already have the patch mentioned then you don’t need to install anything on your system and in many cases use your own use for the testing.

 

IRT feature: Monitor SAP Cloud Platform Integration Content (CPI)

A few weeks ago we added an option to monitor your SAP PI/PO repository content, so you could see what was changed in any objects. And based on the changes you registered you could test the scenarios.

We have also enabled users to test SAP Cloud Integration so it made a lot of sense also to monitor the content so we could support full cycle development. So we can now monitor all changes to the content. So you can see what was changed in a script and what areas were changed in an iflow. The output may be a little technical but it will allow you to see that something was changed.

We also have the ticket content that allows you to register the changes that you are doing and ensuring that you are testing all of the changes that you are making. It is a way to ensure that enables you to document the changes in a better way than using Word documents for the information. You can then link your existing ticket/helpdesk system to the IRT tickets as an extra data source.

You can see a short demo here.

 

There is some features that we will improve in the comparison, so you can see the message mappings content and see the part that was changed. And also improve the comparison of scripts. It will come in a future release.

If you have other wishes to future development do let us know.

First I recommed you to try to install IRT and try it out. You can get started within 30 minutes. Watch the Cloud Platform Integration installation and configuration guide video .

 

Update to testing on SAP Cloud Platform Integration (CPI)

We just released IRT 2.3. That had two big additions. One was our ability to monitor your full SAP PI/PO/CPI development process. In this post, I’ll share the other which is much better support for cloud integration.

In 2.2 we add the first option to run cloud integration tests. We were able to use the new trace functionality for cloud integration to get messages at all stages. This made our test easy to perform without any changes to the setup.

In this, we have added some more functionality

  • We can run regression test for both HTTP and now SOAP adapter. This means that it will use your existing iflow to process the test message in.
  • If you use other adapters or scheduled tasks IRT is able to create a new flow that looks like the original one, except it starts with an HTTP adapter. IRT can record the message from the existing flow.

We have an oss note with SAP that the latest release meant we were getting some problem when setting an iflow into Trace mode.

You can watch the demo video here.

It is pretty simple to setup. Just signup at http://figaf.com/irt then login with the password you will get. Here you can also find the manual. Download the jar file, start it. In the configuration enter your host url, Suser and password, then you can synchronize the list of iflows and start setting up test cases.