SIT test plan, integration test cases and sign-off
Key Takeaway
A SIT phase rests on a test plan, test cases and customer sign-off before testing starts. Test an integration on both sides, not only inside Salesforce.
Integration testing checks that multiple software components work together, so business processes that span more than one system work properly. In an Agentforce Manufacturing project, that can mean an org integrated with an existing ERP, or with an external inventory system that feeds sales agreements. A system integration testing (SIT) phase rests on three things: a test plan, test cases, and customer sign-off before testing starts.
What integration testing covers
Integration tests apply when something in the org interacts with anything that is not native to it. One example is an org that exchanges information with a company's billing systems. If a business has multiple Salesforce orgs, the interactions between those orgs need testing too.
When you integrate with a third-party system, run tests on both sides of the integration, not only inside Salesforce.
In Agentforce Manufacturing, integrations often feed sales agreements. For example, an org can be integrated with an existing ERP so that product, pricing and order information is available in real time.
Inventory data from an external system can also be imported into custom fields on Sales Agreement Product and Sales Agreement Product Schedule. Those fields are then mapped in "Field Mappings for Custom Metrics" so they work as custom metrics. An integration test case for that design can check that imported values reach those fields and show as the mapped metrics.
A manufacturer integrates its org with its existing ERP so that pricing is available in real time. One SIT test case changes the price of a gearbox in the ERP from 300 to 320. On the ERP side, the tester confirms that the change saved and that the ERP's integration log shows it was sent. On the Salesforce side, the tester confirms that the org shows 320. If the org still shows 300, the ERP-side results tell the team whether the problem started in the ERP or in Salesforce.