Enterprise Integration Testing

Browser engine

UI-level enterprise integration checks (SAP Fiori launchpad smoke tests, admin UI validation) should use the qe-browser fleet skill. RFC/BAPI/IDoc/OData/SOAP testing continues to use the dedicated qe-soap-tester, qe-sap-rfc-tester, qe-sap-idoc-tester, and qe-odata-contract-tester agents. See .claude/skills/qe-browser/SKILL.md.

<default_to_action> When testing enterprise integrations or SAP-connected systems:

1. MAP the end-to-end flow (web -> API -> middleware -> backend -> response)
2. IDENTIFY integration points and protocols (REST, SOAP, RFC, IDoc, OData, EDI)
3. SELECT the right agent for each integration type
4. TEST each integration boundary with contract and data validation
5. VALIDATE cross-system data consistency (SAP <-> WMS <-> middleware)
6. EXERCISE enterprise error handling (compensation, retry, alerting)
7. GATE releases with enterprise-specific quality criteria