Skip to content

Fix SoapUI 2.0 initialization and enforce coverage - #4

Merged
loong10k merged 5 commits into
feature/2.0.xfrom
fix/2.0-local-soapui-fixtures
Oct 31, 2026
Merged

loong10k merged 5 commits into
feature/2.0.xfrom
fix/2.0-local-soapui-fixtures

Conversation

@loong10k

@loong10k loong10k commented Oct 31, 2026 •

Copy link
Copy Markdown
Collaborator

Repairs CI on feature/2.0.x. Active public WSDL tests now use a loopback server with existing WSDL/XSD resources and a real SOAP Ping response. The SoapUI core initializes before SoapuiSettingsImpl registers an SSL listener, breaking the proven HttpClientSupport.helper is null cycle. Constructor tests no longer treat initializer errors as success. A deterministic test JVM soapui.home keeps tests self-contained.

Adds behavior tests for HTTP/proxy/WSDL/WSI defaults, SSL settings, and real SOAP Ping submission by operation name/index with Map and array parameters. Restores JaCoCo's Surefire agent and makes the existing 90% target fail the build when missed. Clean local JDK 17 mvn clean verify: 317 tests, 0 failures/errors, 964/1066 lines covered (90.4%), all JaCoCo checks met. Exact-head CI is pending. Production initialization order and test behavior need technical review before merge.

@loong10k loong10k changed the title Use local WSDL and SOAP fixtures in 2.0 tests Fix SoapUI 2.0 initialization and use local WSDL fixtures Oct 31, 2026
@loong10k loong10k changed the title Fix SoapUI 2.0 initialization and use local WSDL fixtures Fix SoapUI 2.0 initialization and enforce coverage Oct 31, 2026
@loong10k
loong10k marked this pull request as ready for review October 31, 2026 20:18
@loong10k
loong10k merged commit 3a24732 into feature/2.0.x Oct 31, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant