SoapUI Integration with AIQ

Recommended guidance

SoapUI supportintegration wasshould removedbe 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

1. Keep SoapUI assets in releaseversion 5.2.0 of AIQ.

   AIQ integratescontrol with SoapUI,clear whichownership.

2. Do isnot anstore open-sourcesecrets webinside serviceproject testingfiles applicationor forshared Simplelogs.
3. Run Objectsmall Accessvalidation Protocoltests andbefore representationalscheduled stateor transfers.high-volume execution.
4. Retire or consolidate redundant SoapUI functionscontent includewhen webService serviceSuite inspection,replaces invoking, development, simulation and mocking, functional testing, load and compliance testing.
   • Running SoapUI as Functional Testit.
   • Running SoapUI as a Performance Test
   • Running Data-enabled SoapUI Test

   ---

Last updated: JulyOctober 25,7, 20242026

If you have any feedback on this topic, please contact us at documentation@appvance.ai