The document discusses the importance of testing in integration systems, outlining the costs associated with inadequate testing and the potential risks to business operations. It introduces the Figaf Integration Regression Tool (IRT) which facilitates efficient testing by recording live messages, running regression tests, and verifying data across systems. Additionally, it highlights the cost savings associated with using IRT compared to traditional testing methods and provides a business case for implementation.

1. Figaf Integration Regression Tool™
Would you like to minimize risks of failure on your system
when implementing changes?
© Figaf 2017

2. Why testing is important?
© Figaf 2017

3. 35% of development cost is testing
• Multiply studies prove that testing account for 30-40% of
development cost in general IT projects.
• My guess for integration it is probably in the line.
• Bug fixing even more

4. © Figaf 2017
• Developer test
• Get test data
• Unit test
• User acceptance test
• Automated test
• Test manager and coordinator
• Test documentation
• Most important takes business time
What costs with the testing

5. If we do not test
• Could be a bomb
• Failure in your business
• Impact relationship with
partners
• Legal
• Cost money
• Support
• Fix problem again
• Change management
• Lost time with business
© Figaf 2017

6. © Figaf 2017
• Not testing enough
• Testing too low complexity
• Skip important tests because too complex
• Need to understand how to ensure data is correct, look in remote
system
• Maybe even involve partners, can take time
Problems with most test

7. My frustration

8. Idea
• Physiotherapy
• Adapter modules
• Create a copy of ICO use for
testing
• PoC
• Get development team
• Challenged to make tool simpler
© Figaf 2017

9. © Figaf 2017
•Record live messages
•Simple way of saving live messages and their output for test cases
•Setup test scenarios
•Reuse existing ICO for the testing
•Run tests
•Running regression tests with the recorded message on test system
•Verify
•Verifying that the original messages corresponds to the test run
What will the Integration Regression Tool do?

10. How the IRT works
© Figaf 2017

11. M
O
D
M
O
D
Operation Mapping
C
O
M
Send
System
Rec
System
M
O
D
M
O
D
C
O
M
Productive/agent system
I
R
T
I
R
T
Test system
JMS queue
Test database
Operation Mapping
M
O
D
M
O
D
C
O
M
I
R
T
Save for
comparison
M
O
D
M
O
D
XI3
I
R
T
© Figaf 2017
Rec
System

12. Request
msg
Mapping Request
mapped
Webservice
Response
Mapped
Mapping Response
Org
Synchronous recording/testing

13. © Figaf 2017
• Quick recording of messages
• Recording on agent systems, run test on local system
• B2B add on EDISeperater sceanrios
• Module and Dynamic Property validation
• Smart comparison of EDIFACT, X12, Text, XML JSON and
Binary/HEX
• Don’t need to sent message to partner
• Works both with sync and async
• Run test in batch jobs
• Dual stack recording
Features

14. © Figaf 2017
•Check if everything works when applying
support packages
•Check when changing mapping to make sure
nothing is affected
•Migration
•Reduce Risk in projects
Why use IRT

15. © Figaf 2017
Reports in Excel about Errors

16. What is tested with IRT
Covered
• Sender Modules
• Routing
• Mappings
• Receiver Modules
• Dynamic properties
• Synchronous messages
Not Covered
• Native communication outside
of the Java system like the raw
SOAP or IDOC calls
• Lookup values are not cached for
updates
© Figaf 2017

17. Business Case

18. © Figaf 2017
Hourly cost 80
Number of ico 200
Changes pr year 300
Number of
support packs pr
year 2
Assumptions

19. © Figaf 2017
Testing price
Time required
pr instance
Number of
ICOs Hours Price Pr year Cost pr year
Normal PI testing
Test an interface when changing mapping 120 1 2 160 300 48.000
Support packs installations testing 60 200 200 16000 2 32.000
Total 80.000

20. © Figaf 2017
IRT testing
½
Time required
pr instance
Number of
ICOs Hours Price Pr year Cost pr year
Normal PI testing
Test an interface when changing mapping 120 1 2 160 300 48.000
Support packs installations testing 60 200 200 16000 2 32.000
Total 80.000
Testing with IRT
IRT server 30.000
IRT installation and configuration 5.000
IRT create test cases 10 200 33 2667 1 2.667
Test an interface when changing mapping 5 1 0 7 300 2.000
Support packs installations testing 10 800 2 1.600
Total with IRT 39.667

21. © Figaf 2017
Time required
pr instance
Number of
ICOs Hours Price Pr year Cost pr year
Cost of not testing
Support cases 240 1 4 320 30 9.600
Rollback and start over 20000 0,3 6.000
Lost business because of errors 20000 1 20.000
System down 2 100000 0,5 50.000
Total for errors 85.600
Not testing

22. Use cases

23. Migration project
• Had to find a way to record productive messages
• Process them on test system
• Compare them
• For all scenarios lots manual work
• Not sure if it is tested correct

24. Patching
• Had to patch a PI system to latest patch
• Tested a bit around to figure out if something had changed.
• By conscience other developer was having abnormalities between D
(new SP) and QA (old SP)
• If not found on test we big production issue.

25. Everyday support
• When ever a bug has been fixed or new feature has been implanted.
• See if it break existing functionality.

26. Figaf.com/IRT
Get a free trial today
© Figaf 2017

27. FAQ
© Figaf 2017

28. What if Figaf stop supporting tool
• Code will be deposited with escrow service so you will be able to get
the code and update bugs

29. Maintance
• 20% yearly to get updates and support to the tool

30. Versions Supported
• Support SAP PI/PRO 7.31, 7.4 and 7.5

31. Dual stack
• We are working on dualstack recording. To record ABAP to Java
adapter, and Java adapter to ABAP.
• Select sender/receiver agreements. Then select ICO for running test.
• Other message fetched thru RFC/SOAP

32. Multiply systems
• What if I want to run IRT on both DEV and QA
• For testing purposes of IRT you will be able to get a free extra license
for your development system with a limit of 50 ICOs.
• If you want to perform full testing then second system is with 50%
discount.

33. Performance impact
• If module is on a communication channel it will cost <1ms if not
recording
• Recording will cost 3ms for processing in the module
• Total sync performance delay 12ms
*Depending on processor speed

34. Figaf.com/IRT
Get a free trial today
© Figaf 2017