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
Support for MessagePact? #162
Comments
Hi @neilcampbell @bethesque please can you look into this request? |
Hi @vikasillumina Sorry for the late reply. |
Is this something that is being considered by the PactNet team? If so, is there an ETA? Otherwise, would you be able to explain why it won't be supported? |
Yeah it would definitely be a nice addition. No ETA unfortunately, I haven't yet looked into what is involved or if the ruby core that we currently use even supports it yet. I have asked a couple of questions and will report back the findings. It would be awesome if someone here is interested in adding support? |
pact-foundation/pact-ruby#177 (comment) Potentially not something that's feasible to be worked on until the move to a Rust implementation? (based on the above comment). I'd be willing to contribute to the effort, however i'm unfamiliar with Ruby and if that's required it might be more quickly accomplished by someone within the pact-foundation team. |
Apparently the ruby core does have support. There is a PoC and some more info https://github.com/pact-foundation/pact-message-demo and https://gist.github.com/bethesque/c858e5c15649ae525ef0cc5264b8477c if you'd like to take a look? |
H , |
Any update on this? Would supporting message contracts also imply supporting the 3.0 specification as a whole? |
Hi, @bartschotten. |
Is there any ETA on when this will be released? |
You can build/publish the branch yourself (#175). I've been able to get it to work for some basic scenarios. |
Thanks @bartschotten I have downloaded it myself and followed the
I have set up the |
@carl-thomas Setting up the XUnitOutput won't fix the exception. That exception is just letting you know there is an error and "If" you can't see the details it's because an Outputter hasn't been set up to write it out. If you have done it correctly, you should now see the underlying error that was occurring. |
@neilcampbell I just ran the code on a Windows OS and the tests pass successfully. I was using |
@neilcampbell @bartschotten do you have any idea why this would not run on MacOS? Do you have any ideas where this issue could be coming from and how I might be able to solve it? Thanks |
@carl-thomas I'm not sure, we probably need a bit more information about the error you see. |
@carl-thomas Could you check with the latest version of the branch? I've fixed an issue on Linux, which I suspect could also solve your problem. |
@neilcampbell , any plan to merge the "message-pact" branch back to master in near future? |
This support will be added in 4.x |
Hi @neilcampbell @bethesque ,
We have few Microservices talking to each other via Kafka topic messages only, no direct interaction.
We want to do contract testing for these message interactions. I looked for few examples on how people are doing this and found example like this:
https://dius.com.au/2017/09/22/contract-testing-serverless-and-asynchronous-applications/
So they are referring a MessagePact, is this supported in Pactnet?
Regards,
Vikas
The text was updated successfully, but these errors were encountered: