SoapUI Integration with AIQ
Recommended guidance
SoapUI integration should be treated as legacy or customer-specific unless it is actively required. For current API testing, prefer Service Suite when it can cover the same requests, assertions, data handling, and reporting.
Integration review points
- SoapUI project location, version, plugins, dependencies, and execution host.
- Endpoint configuration, authentication, certificates, proxy, and firewall rules.
- Data sources, DPL mappings, assertions, and expected artifacts.
- Pass/fail mapping between SoapUI results and AIQ execution status.
Maintenance guidance
- Keep SoapUI assets in version control with clear ownership.
- Do not store secrets inside project files or shared logs.
- Run small validation tests before scheduled or high-volume execution.
- Retire or consolidate redundant SoapUI content when Service Suite replaces it.
Last updated: October 7, 2026