Blog > Michal’s Tips: Stop testing your interface scenarios – you’re not doing it anyway right

Michal’s Tips: Stop testing your interface scenarios – you’re not doing it anyway right

Michał Kowalczewski Int4 IFTT Product Manager, SAP Press Author
icon__calendar 2016-07-04


When we’re starting a project both functional consultants and developers are both responsible to describe a set of test scenarios which always need to be executed to check if the interface is working properly. Functional consultants will put all important business scenarios which need to work and developers will update those with some cases where they know the interface is being developed in a complex way (multiple lines, summarizations  and other complex mapping logic). Thanks to this cooperation we can get a pretty decent subset of integration scenarios which once run will make sure the interface scenario is working perfectly. Running all of the prepared test scripts needs to happen in a few project phases:

  • during the first integration testing phase (when the interface is being executed end to end for the first time ever)
  • after we implement each change to the interface scenario during integration testing, user acceptance testing and any other testing phase which may be performed in between those two but before the first golive
  • after golive when we need to fix any existing scenario or add any new functionality to it

How does that look like in reality

(at least from my 12 years of experience with >25 clients) .

  • during the first integration testing phase we need to check all possible scenarios, otherwise the interface would not wor
  • after we implement each change to the interface scenario we’re usually in the middle of “rapid” development where everything needs to be finished ASAP and in many cases the development was already approved so testing is only run with a subset of the subset (maximum 1-2 testscripts)
  • after golive when we need to fix any existing scenario or add any new functionality to it the we have a few choices:

– hot fix – needs to be done immediatly (ASAP is too slow) – so we fix, run a test case and move to production (praying that it till not cause any failures to any other scenario)

– new functionality – depending on the possible lead time, a small change can either be implemented if the lead time is small (meaning we don’t test too much) or we don’t implement the change (as testing team needs to run all possible test scripts and it takes 10 days to do it so business realizes they can live without the change – sad but also happens)

What does that mean in reality?

That we only have two choices:

  • we can either push for running all prepared test scripts but risk huge project delays or simply rejecting any changes to the existing interface scenarios
  • we can stop testing (vide articles’s title) and run one or two test scripts and keep on praying when we transport to production environment

What is the reason for that? I’ve been asking myself the same question many times and I came into the conclusion that it’s because of lack of interface scenario testing tools. I’m not saying that they don’t exist, I’m only saying that they do not respond to the needs of both business and developers. What would those two groups need ? I’m hoping for your input for the same but let me just present my short list.


  • being able to run a full set of interface scenarios tests with a single click after implementing each change without waiting for anyone else (especially from the bus
  • not having the need to going to any transaction/entry screen as the module knowledge cannot be mandatory to retest an inteface after the change
  • being able to test the interface both on development and on quality boxes (not only on quality after the change is transported)


  • being able to record a test script case from any existing document which was processed in the past and was posted correctly without the need to recreate it again
  • being able to be sure that all of the fields will always be validated (and not only the ones selected during the initial test script preparation)
  • test script execution in backgrund everyday validating all transports and changes done by the developemnt teams (as the latter can often change and may not be aware of what needs to be retested from te technical perspective)


Would anyone have any inputs on this topic? It would also be possible for me to organize a session (SAP Mentor expert table) at SAP Teched 2016 (Barcelona or Vegas) if someone would be interested to discuss how to test/retest integration scenarios or to show how it’s being done at their company. I’d kindly ask you to provide any input if you think this is a valid but not that much discussed topic.

Important info:

If the testing process looks completely different then described please do let me know as I can only tell what from what I’ve experienced.

Michał Krawczyk – SAP integration consultant since 2004. He has been recognized by SAP included becoming an SAP Mentor in 2007 and winning the top contributor/topic leader award from SDN (SAP Developer Network portal) in SAP PO/PI eight times. Michal is the author many SAP integration related books.

Michał Kowalczewski Int4 IFTT Product Manager, SAP Press Author
SAP integration consultant & architect, team leader and project manager since 2005. Experienced in all leading SAP integration technologies (SAP PI/PO, ALE, HCI, BRF+, Enterprise Services, ABAP). Int4 IFTT Product Manager. In the past he was also involved in SD and CRM consulting. Accomplished more than 20 projects, both full cycle implementation and improvement projects. He holds a master?s degree in computer science and econometrics and is an SAP-certified solution and development consultant as well as SAP PRESS author. Business integration improvements, highly focused on the business processes, deep knowledge of ECC backend and SAP configuration (ALE, SD, MM, FI), advanced ABAP and PI/PO programming, strong leadership & management skills.