Interface migration with Test Driven Development

Once the integration test cases are ready and validated, the next step is to start and complete the development of the SAP CPI iFlows.

In order to ensure that the CPI developments can be conviniently tested, and to enable them for test automation, please observe the relevant development guidelines and best practices. We can recommend SAP Best Practices document from SAP Blog: Comprehensive SAP CPI Guide for Standards & Best Practices

Two approaches to ICO to iFlow migration

Int4 Suite support two approaches to the migration - manual and automated. The manual migration assumes that all the work on the migrated iFlow will be done by development team. For the automated migration, Int4 Suite can create iFlow content for most of the ICOs existing in modern SAP PI/PO setup. Please note that automation of migration of BPM’s or ABAP-based mapping solutions is not possible with Int4 Suite.

Regardless of the chosen approach, Int4 Suite Migration Cockpit will automate creation of Automation Object and migration of test cases from SAP PI/PO to SAP CPI.

Please read on these following topics to proceed

Once the migration preparation is done, further development and testing, including Test Driven Development approach can start.

Read more about Test Driven Development in this section of the manual: Test Driven Development with Int4 Suite