<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/2fccee2bf93746b0a4e7e7c07e6a44b3&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/2fccee2bf93746b0a4e7e7c07e6a44b3-60116c0ee5e2e636.gif</thumbnail_url><duration>215.967</duration><title>SAP Integration Suite Pipeline Concept testing with Int4 Suite</title><description>This Loom explains how to test the SAP pipeline concept end to end using a single test case. In an inbox scenario, the input for a test is the payload captured at the entry outflow, and the expected output is taken from the target outflow after all transformations and logic. The example shows 11 independent test cases, each bound to the same automation object, with separate configuration for an entry automation object (source iFlow details) and an output automation object (target iFlow details and block to fetch). Execution works like standard testing, where I and T4 suite injects messages into the entry iFlow and retrieves outputs from the configured target iFlows.</description></oembed>