You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 7, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 7, 2026. It is now read-only.
Hello,
Spring Cloud Contract WireMock by default resets stubs, scenarios, etc., after each test class.
Unfortunately, this prevents tests from running in parallel. Very often, when one test class finishes, it resets the stubs of other tests still running in a different thread.
Some time ago, @marcingrzejszczak introduced the flag wiremock.reset-mappings-after-each-test, which allows forcing a reset after each method.
Wouldn't it make sense to introduce a similar flag that allows disabling resets after each class?
In my opinion, these resets don't make sense at all.
If someone needs them, they can explicitly trigger a reset in @after method executed after each test/class.
Hello,
Spring Cloud Contract WireMock by default resets stubs, scenarios, etc., after each test class.
Unfortunately, this prevents tests from running in parallel. Very often, when one test class finishes, it resets the stubs of other tests still running in a different thread.
Some time ago, @marcingrzejszczak introduced the flag wiremock.reset-mappings-after-each-test, which allows forcing a reset after each method.
Wouldn't it make sense to introduce a similar flag that allows disabling resets after each class?
In my opinion, these resets don't make sense at all.
If someone needs them, they can explicitly trigger a reset in @after method executed after each test/class.