← All features

Testing

Baseline testing with third party tools

Your Tricentis tests create a purchase order, but nothing checks the SAP integration messages that order triggers.

Many companies already test their business processes end to end with tools such as Tricentis. Baseline testing lets those test cases also check the SAP integration flows they trigger. Instead of Figaf sending the test message, the sending system creates it, and Figaf compares the processing with a recorded baseline.

How it works

  • The other tool sends the message. In a baseline test the sending system, driven by your test tool, creates the messages. Figaf then compares that the same messages are sent and processed, and in the same order.
  • Record the baseline. For example, you run a Tricentis test case that creates a purchase order, which is sent to SAP Integration Suite. You record the resulting message in Figaf. The iFlow triggered should always look the same.
  • Correlate by document number. The iFlow must log the PO number in the Application ID, so Figaf can link the messages to the document.
  • Extend the test case. Your purchase order test case then calls Figaf to start expecting messages for a given scenario, triggers the PO test case, sends Figaf the link between the old and the new PO number, and checks the result in Figaf.
  • Timing. It can take some minutes for Figaf to return a testing status.

Business value

  • One test covers the whole chain. The business test and the integration check run together, so an order that is created correctly but sent wrongly is caught in the same run.
  • Reuse what you have. Existing test cases in your test automation tool are extended, rather than building a separate set of integration tests.
  • Fewer surprises after changes. Comparing against a baseline shows when an iFlow starts processing a known document differently, before the change reaches production.
  • Less manual checking. Testers do not need to look up the related messages in SAP monitoring by hand to confirm the integration worked.

Good to know

  • Baseline testing is part of testing in the Figaf DevOps Suite and the Figaf Testing Tool. Baseline test cases have existed since IRT 2.2, built for tools such as HPE UFT that send messages to SAP PI/PO, and are also used for testing SAP Cloud Integration.
  • Correlation of messages by document number was added in release 2509.
  • Related features: regression testing.

Learn more

Included in

Figaf DevOps Suite

Extend your business tests to cover the integration layer

Let a third party test tool trigger the message, and have Figaf check that the iFlow processed it the same way as the recorded baseline, correlated by document number.

See baseline testing with third party tools on your landscape

No credit card required.

Integration cost calculator →

Start your free trial

No credit card required

Try Figaf DevOps Suite free for 30 days. It takes less than an hour to get started, and we send everything you need by email.

Join our newsletter

Get the latest about Figaf, SAP and anything relevant to SAP integration, every week in Figaf Weekly.