Save your time and money by automating key testing procedures with Int4 IFTT. Use our Savings Calculator and see how much you can reduce the costs of project development.
Number of interfaces:
Average number of test cases per interface:
Time effort per interface test case preparation
60 min | 10 min
Total time in day for test cases preparation
87 MD | 14 MD
Time effort per interface test case execution
60 min | 1 sec
Total time per full cycle regression testing
87 MD | 2 hours
Creates test cases based on the real documents existing in your SAP system
Enables to run test cases as many time as you wish, whenever you want
Test your business flows independently of the external systems
Robotic Crawler for fetching existing electronic messages for many integration scenarios
Int4 IFTT is a script-less SAP API testing tool that secures the growth of companies eliminating the risk related to manual entering of data. The tool automates API integration testing for:
increases the speed of action and saves your valuable time. Thanks to the virtualization of connected systems, testing of SAP environment undergoes without third-parties involvement. Int4 IFTT lets you run all tests independently providing you the best conditions for development.
After pressing the start button, your work here is done!
It’s time to see how Int4 IFTT capabilities perform in real life. Check out these few scenarios to gain a more in-depth understanding of the tool’s functions and the cases in which it was applied.
Learn how the Int4 IFTT software takes care of every aspect of the testing process. Also, feel free to reach for resources we’ve prepared to help you better understand the tool.
It ensures the quality of every change introduced to application interfaces and reduces the risk of introducing changes in the area of SAP Integration thereby offering tremendous time and costs savings throughout different testing phases.
Int4 IFTT goes further to fill the gap for automated testing on SAP integration platforms and can easily be integrated—and—used in conjunction with other Testing Suites.
And for the cherry on the cake, instead of simple API testing, we have come up with a unique approach for an end to end application interface testing, that not only covers the full SAP landscape, but also all technical and business components.
In retrospect, if you fall under the category of people who prefer to just read, as opposed to video presentations. We also have something for you. Our blog comprises written publications of our very many SAP experts. So don’t be shy to help yourself.Start reading
Our mentors and staff in the flesh—hypothetically speaking. If you happen to be one that fancies video presentation rather than reading, then you are in for a captivating, but yet educative screen time.
You can check out published videos of our experts here.Watch
For people that aren’t interested in the grand scheme of things but rather, are interested in finding specific facts, knowledge, terminologies, SAP abbreviations, etc. We are sure you will enjoy this section then.Open Int4 IFTT WIki
Int4 IFTT is designed for companies that run their business on SAP systems with multiple core processes operating in 3 rd party systems integrated with SAP:
Yes, Int4 IFTT has been successfully certified by SAP for integration with SAP S/4HANA on-premise edition 1511 via the SAP integration scenario ABAP Add-On Deployment for SAP S/4HANA (certification number 8681) and certified for integration with SAP NetWeaver 7.40 via the SAP integration scenario ABAP Add-On Deployment for SAP NetWeaver (certification number 8670).
The process of a test case creation is very efficient because the existing documents, previously created by the interfaces, may be reused. In a typical scenario, the tester picks up interface messages for documents created during the user acceptance test and bulk uploads them. Additionally, assertions are defined per document groups (e.g. sales order, outbound delivery, financial posting, etc.). There is no need to define them each time when a test case is created. Moreover, based on the Int4 IFTT configuration, the assertions will be applied to test cases automatically.
We can distinguish a few Int4 IFTT user groups. They are for example:
There are two models of Int4 IFTT licensing: a free trial period license and a full license.
From a technical point of view, Int4 IFTT is a regular ABAP add-on to the SAP system and modifications of functionalities or extensions can be done by customers on their own or with implementation partners, just like with any other custom code in the customer’s system. Int4 doesn’t recommend own modifications and is always happy to help with implementations of new client-specific functionalities.
We are the authors of an openSAP course “Virtualize and Automate Your SAP Testing Using Int4 IFTT” (over 5000 enrollments). In this online training, you will learn more about our solution. We’ve created special Int4 IFTT Learning Paths to help you get the answers you’re looking for fast and successfully. Watch the lessons that we recommend and learn more about Int4 IFTT.
Int4 IFTT is a tool which was designed to be used to test SAP middleware (SAP PO, SAP CPI, SAP AIF, IDOC, proxies, also for S/4HANA conversions, etc.) where it can be fully scriptless (no need to create any test data as we use existing messages or backend documents posted on the SAP backend systems). It can be used in all sorts of migrations/patching/service pack upgrades/rollouts where it’s not possible to create test cases manually as with other testing software. On the other hand, Int4 IFTT can be called via API from any Test tool like HP/Microfocus ALM, Test Suite, etc. for test result analytics and this kind of integration we do in all of our projects as integration testing is a good way to start the testing journey but the journey needs to be continued with other types of testing too. With Int4 IFTT we also test different phases of the projects (more the Unit Testing and Integration Testing and less for UAT). From the functional perspective, Int4 IFTT can also virtualize external systems (legacy, B2B). So to conclude, Int4 IFTT is a more detailed engine for running the Test Suite if your company heavily relies on integration with other systems. Int4 IFTT is an SAP certified add-on installed on Solman (just like SAP Test Suite).
In our openSAP course ” Week 3 Unit 6 (last one)” we’re describing:
Seeing that in DevOps a small team is recommended for efficiency we’ve designed Int4 IFTT in a way it’s easy to be used by 3 types of people:
Int4 IFTT and CBTA serve two different purposes:
However – in case Int4 IFTT needs to simulate a complete SAP End to End process for integration flow where a certain activity needs to be done manually in SAP like:
Int4 IFTT can use (as one of the steps) ecatt or any other screen recorder (CBTA) and the same applies – any test in ecatt/CBTA can call Int4 IFTT to do an integration scenario test (via Int4 IFTT API).
Int4 IFTT can be and is very often used without SAP PO/CPI as shown in the S/4HANA conversion and ABAP backend lessons as it has IDOC, Proxy, AIF adapters. So you don’t need any middleware but still can test all SAP integration scenarios based on IDOCs, Proxies and SAP AIF. This is also a standard way how we test S/4HANA conversions as the demo system for conversion does not need to be connected to any middleware but still, we may want to test some scenarios.So the answer to this questions is: yes, we work like this quite often without SAP PO/CPI as Int4 IFTT is testing both parts of an interface middleware + backend implementation (they can be tested together or separately).
The functionality which handles that in Int4 IFTT is called Landscape configuration where you configure all systems with their respective names (as in SLD) so the changes are happening on the fly during test case execution. It’s described in our openSAP course – Lesson 1 of Week 3 in more detail.
Int4 IFTT is an SAP certified ABAP addon so you can deploy it on any ABAP based system (like ECC, S/4HANA). We, however, recommend to deploy it on SAP Solution Manager as a central instance connected to all existing systems.
Yes, there are alternatives to include UI testing in Int4 IFTT (as for this eCATT is used). In week 3 of the openSAP course, you will see Int4 IFTT API that allows for calling test cases from other testing tools like CBTA, Microfocus UFT, Tricentis Tosca. In such a case, the record & playback function will be delivered by them, and the application interface test cases will be executed and validated by Int4 IFTT. The difference is that test case orchestration will be maintained in the external software.
Int4 IFTT is used mainly for test automation of integration flow scenarios (virtualization of sender systems like B2B, legacy, etc. and then comparing the final result: either message after mapping or the final business document created in the backend system). At the same time, Int4 IFTT supports ecatt for UI flows (for example, when you build a process like order to cash in Int4 IFTT’s EDI order, EDI ASN, EDI invoice but one of the steps like ASN creation needs to be done manually and not with the interface, Int4 IFTT uses ecatt for doing that). Those kinds of processes will be shown in Week 2 and Week 3 during lessons with ABAP backend support. So to conclude Int4 IFTT is doing integration flow testing and not UI scripting (ecatt), about cbta (we will probably add its utilization in Int4 IFTT) but due to the scriptless nature of Int4 IFTT (tests are created from real messages and don’t need to be done manually), it’s not a priority right now.
SAP E2E means we only test all SAP applications (SAP middleware: SAP PO, SAP CPI + SAP business systems, ABAP code, customizing, SAP AIF, business documents). So all non SAP systems are completely virtualized hance not required for the test. This means since SAP is in most cases the most “changed” system, we want to make sure we at least have it tested (so bank, EDI system, other legacy applications are not required to run the test at all: as those are virtualized by Int4 IFTT). This kind of approach is very important for us as we want to enable earlier stages of testing. Many companies don’t have any automated testing but they want to start with full E2E flows which in most cases fails due to the complexity and maintenance later one. We believe it’s easier to start with testing just SAP system and only do something more once you have this mastered.
SAP PIT was designed for a single purpose only: to help developers do the SAP PO migration. Int4 IFTT, on the other hand, was designed to help to implement continuous testing across all SAP middleware technologies, so SAP PO migrations are just one of the many different use cases.
As for the Solman version: Int4 IFTT can work with any available version of Solman.
There are many use case scenarios supported by Int4 IFTT: