-
-
Notifications
You must be signed in to change notification settings - Fork 480
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REST and plugin test targets are not working in the same test #1819
Comments
@rholshausen I tried using 4.5.13 however I encountered a problem with states when running this code:
I have 2 state change handlers added via switching between the test target type in setTarget and addAdditionalTarget didn't change anything On a different test class that has 2 state change handlers (and doesn't use |
I can't replicate this. In my test project, the state change methods get called. Can you provide the full statck trace? For instance, if I comment out the state change method on
and then, if I re-enable the state method on |
|
@rholshausen I think I found my mistake - a silly copy-paste one involving a misplaced comma. no need to look into this any further. |
No problem, it's all good if it is working for you. |
Yes, this seems to work with http and gRPC test targets. |
I'm trying to run 2 technological stacks on the same provider test:
all of the REST tests failed because Pact couldn't find the REST target with
Verification Failed - transport error
when I reversed the order of declaration (
HttpTestTarget
as target andPluginTestTarget
as additional target) the gRPC parts of the test yieldedgRPC interactions must be of type V4 synchronous message, got V4 Synchronous/HTTP
I suspect that there is a bug in the mechanism that iterates through the
TestTarget
s and decides which one to use for the interaction that is causing the "additional" targets to not work with this mix of technologiesI'm using ProviderJVM 4.5.1, JUnit 5 and Spring
Slack thread
The text was updated successfully, but these errors were encountered: