has joined #pact-net

has joined #pact-net

/github subscribe pact-foundation/pact-net issues releases pulls

/github subscribe pact-foundation/pact-net issues releases pulls

/github unsubscribe pact-foundation/pact-net deployments public commits

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hi, I have a problem with PactNet.Windows 2.3.0. Tests run perfectly on local machine but fail with this error on VSTS: ...pact-win32/lib/ruby/lib/ruby/gems/2.2.0/gems/bundler-1.9.9/lib/bundler.rb:418:in `[]=': Invalid argument - ruby_setenv(GEM_PATH) (Errno::EINVAL)

has joined #pact-net

Hm. That's going to be tricky to fix. Is there such a think as a free open source VSTS account? Also, can you raise an issue in pact-foundation/pact-ruby-standalone if you haven't already. @gxsham

has joined #pact-net

Yes, you can create a free vsts account and use their agents for free, the only limit is the team size - up to 5 people

I can fix the underlying ruby code (it's packaged as a standalone executable) but I have no experience in dot net or VSTS - would you be able to create a VSTS build that recreates the issue @gxsham?

Yes, I will try today to do it today

is there a simple example of using a regex verify a provider response in http://pact.net?

@richard.peckett it should be the same as for a request.

Or are you asking in general about matchers?

@richard.peckett https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs#L288

Is that what you are after?

has joined #pact-net

Nulls should just do an exact match. What error are you getting?

@beth I got next error in pact logs: ERROR -- : No matching interaction found for PATCH /api/facets/export/data ERROR -- : Interaction diffs for that route: ERROR -- : Diff with interaction: "A request to get export data" Diff -------------------------------------- Key: - is expected + is actual Matching keys and values are not shown "body": { + "AnswerId": null, + "FileName": null

You have some extra fields in your request

You need to define them in your expectations

@neil thanks, I'm guessing that works exactly the same for the provider?

I see in fiddler that request contains key "FileName" with null and I expect null value

but pact return error when compare

Can you put the test code that you're executing, and the full logs into a gist please? There's not enough information to diagnose the issue from your explanation.

ok

I?m not 100% sure what you mean? Do you mean when the provider verification runs against that pact file?

@bethskurrie Do you mean project or only pact test?

Just the pact test and the full mock service logs for now. I should be able to see what's going on.

@vk.regs your fixture representing your expected request does not have a FileName in it ``` { "NonIncludedMetaFields": [ "ISESDOORGCIV", "ISESDOORGGR", "ISEORGCIV", "ISEORGGR", "ISEORGMIL" ], "ExportFormat": "XlsX", "DateTimeFormat": { "ShortDatePattern": "M/d/yyyy", "MonthYearPattern": "MMMM, yyyy", "ShortTimePattern": "h:mm tt", "TimeZoneOffset": -180 }, "BaseUri": "https://tewb.ihs.com/", "DisplayQuery": "laser" } ```

But your actual request does.

The error message you are getting is saying "you have FileName : null and AnswerId : null in your actual request, but you didn't declare them in your expected request"

I specified FileName equal null in expected request directly

Well, it's not coming through ``` I, [2018-06-20T10:45:50.325316 #5672] INFO -- : Cleared interactions for example "" I, [2018-06-20T10:45:50.573464 #5672] INFO -- : Registered expected interaction PATCH /api/facets/export/data D, [2018-06-20T10:45:50.584464 #5672] DEBUG -- : { "description": "A request to get export facet data", "request": { "method": "patch", "path": "/api/facets/export/data", "headers": { "Content-Type": "application/json; charset=utf-8" }, "body": { "ExportFormat": 3, "DateTimeFormat": { "ShortDatePattern": "M/d/yyyy", "MonthYearPattern": "MMMM, yyyy", "ShortTimePattern": "h:mm tt", "TimeZoneOffset": -180 }, "DisplayQuery": "laser", "BaseUri": "https://testapp.com/", "TestMode": false } }, "response": { "status": 200, "headers": { "Content-Type": "application/json; charset=utf-8" }, "body": { "Format": 3 } } } ```

looks like pact ignore null variables

No, it doesn't.

Unless something in .net is doing that.

@neil is it possible that keys with null values are not being written in the request?

Yeah that is quite possible

As I understand one way to verify such request use Match.Type for each field

The log also says that it's getting an unexpected getting "+ "AnswerId": null," which I don't see anywhere in the code @vk.regs

@bethskurrie I modified initial request to make it more simple

As I understand one way to verify such request use Match.Type for each field?

@vk.regs can you create a git repository with an executable example that demonstrates your problem, and raise an issue in pact-net please? Or, fork pact-net and create a test case that demonstrates the problem. That way @neil can easily identify if there is a problem with the pact-net code.

Thanks. But it hard because we use internal libraries and I never created GIT repository before. I will try later

Ok, how about forking pact-net, and creating a test case in this test to demonstrate your issue? https://github.com/pact-foundation/pact-net/blob/master/PactNet.Tests/Mocks/MockHttpService/MockProviderServiceTests.cs

@vk.regs This looks to be an issue with the way pact-net handle null values. I am publishing a fix now. Nuget package version 2.3.1 should fix this issue.

@neil thanks

Should be released in the next 30mins or so

:+1:

has joined #pact-net

Hi everyone :wave: I have a question about provider side... If I understand correctly, I must have *up and running provider service* in order to run pact verification test. If that is correct, should I be running provider service on `Microsoft.AspNetCore.TestHost` or on full blown `kestrel` web server?

Hi @borkke. From memory there were issues talking out of proc (the ruby core, makes the HTTP call in v2) to the server running using TestHost. Worth testing to see if it works. But yeah I?d recommend using the full web server. You can see https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Provider.Api.Web.Tests/EventAPITests.cs for an example. It doesn?t use Kestrel though.

Thanks @neil.. in that case, do you know is it possible to run pact verification tests in CI server, against provider service which is running inside a build context?

From all documentation I found, it seems like I need to make sure to have up and running provider service, and that makes me think I have to have some "testing" environment where I first have to deploy my service provider and run pact verification (this kind of goes against my understanding of the purpose of contract testing :thinking_face:)

Nah no need for a seperate test environment, you just need to start the webserver via the test suite on the CI/build agent that runs the tests

In the example project inside the pact-net repo we do this. We use AppVeyor to run the CI process for pact-net itself, and the sample project tests are run as part of this.

That's really good news.. I was hoping to hear that

Thanks again!

Could somebody help me to understand what such warning mean in provider test that failed on array verification WARN: Ignoring unsupported matching rules {"min"=>1} for path $['body']['Items']

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

hey all - does there exist an equivalent .net version of the can-i-deploy feature (which checks the matrix to determine whether things can be deployed)?

@tmok01 Nah there is nothing in the .NET version that does that at this stage

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hi all, I am trying to write consumer tests with pact for dotnet core. After enabling SSL for MockProviderService the test fails with "System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure". I've seen in the documentation that it is recommended to ignore certificate validation errors globally due to a self signed certificate, but HTTP client for MockProviderService initializes inside the pact lib, so the only way I have currently found to make it work is to add handler.ServerCertificateCustomValidationCallback = (message, cert, chain, errors) => true; directly into the pact-net AdminHttpClient constructor. It also required changing type of handler parameter from HttpMessageHandler to HttpClientHandler and switching target framework to .net standard only, as .net framework doesn't have ServerCertificateCustomValidationCallback method for HttpClientHandler. Can anyone please tell, is there any simpler way to get SSL connection working in dotnet core project?

Hi @raido.letterbox. I?m not too sure what?s involved in getting it working on .NET core TBH, I haven?t been doing much .NET lately. In standard .NET there is a global config via ServicePointManager which should work, however I?m not sure the same exists in core.

Probably the correct way to sort this is to allow a custom cert and key to be specified, so there are no SSL validation issues. The pact ruby core already supports this, I just haven?t passed those options through as it will need some testing and doco.

Hi Neil. Thanks for the reply. I have tried ServicePointManager, but it doesn't seem to work in core :disappointed: As for the custom cert - not sure that I understood correctly - is this feature planned to be added to pact-net after the testing?

has joined #pact-net

Damn, that?s a pain. The idea was that Pact-Net would support the custom cert, however I just haven?t gotten around to it yet.

has joined #pact-net

Hello! I have a silly question (probably my noobness) but I don't understand why I need a Platform Specific core engine. ex. PactNet.Windows

@antonios.klimis Hey! Good question. PactNet wraps the ruby standalone core, and that has platform specific packages (and each package is quite big). If it was just .NET, we wouldn?t need seperate packages.

Thank you @neil! When I want to test it in a Linux environment how do I handle that? I use http://asp.net core within Linux containers. Out of curiosity, will that ruby core sometime with be port to .net ?

You can install more than one platform specific package. PactNet will load the correct package depending on the runtime environment.

Nice!

We originally had a native .NET implementation, however moved to using the shared ruby core as it makes supporting new features more consistent across all the Pact language implementations.

Ideally we want to move to using the rust core, as it should be a lot lighter weight

Alright! I'm very keen to contribute. Where do you think is the right place to start? (Maybe that's not the right channel to ask (?))

Awesome!

Probably the best place is to checkout the issues on GH and see if any of those interest you

set the channel topic: https://github.com/pact-foundation/pact-net

I?m just about to add another issue to add support for custom SSL certs (based on a conversation above in this thread)

Ok, I'll have a look when you add the issue. In the mid-time I will clone the repo. :slightly_smiling_face:

Yep good idea :smile:

I?ll probably add it later tonight (Perth time), as I need a bit more headspace to write it out in a coherent manner :smile:

No worries! I need my time having a look around. You are 5 hours ahead Greek time.

Hi. I have been browsing through pact-net workshop and found there a mention of _mockProviderService.VerifyInteractions() method which is not present in .net Core workshop. According to the comment, it verifies that interactions registered on the mock provider are called only once. I have tried to intentionally make the same request twice in the test with this method, but the test didn't fail. (My test project targets .net Core) Can somebody please tell, what exactly does this method check, maybe I have misunderstood the concept?

@raido.letterbox Sorry for the confusion. Before we moved to using the ruby shared core, it would validate exactly once. Now with the ruby core it validate on an at least once basis.

But your understanding is correct, it validates that the interactions you have registered on the mock provider service have been called from your test.

I have just updated the Readme

Thank you!

has joined #pact-net

has joined #pact-net

has joined #pact-net

@neil Beth suggested to seek your help on this question https://github.com/seek-oss/seek.automation.stub/issues/11

If you can provide an example it will be great

Hi @vikassd2012. Will have to look into that library and get back to you

Thanks @neil :+1:

peeps I can't seem to get more than one interaction on my pact file, it's always taking the last test that ran and uses that as the sole interaction on the file what am I doing wrong?

Are you creating a new instances of the mock provider service for each test?

It should be shared between tests

Yeah, sorted this now it was the way I was using XUnit, switched to NUnit as it works better for the way I'm structuring my code, cheers Neil.

:thumbsup: Awesome. Sorry for the late reply

has joined #pact-net

Hi I'm currently looking at v3 of the Pact Specification as part of a re-architecture at my place of work as this is heavily based on Event-Driven Architecture and messaging. I noticed that v3 hasn't been implemented yet for .Net and wondered what the current state of this is (You've probably had this asked a number of times so I apologise in advance)? The reason I ask is that myself and a couple of colleagues have been discussing the possibility of implementing v3 ourselves and was wondering... 1. Is the v3 specification complete? 2. Has the development of v3 .net implementation started yet? 3. How can I and my colleagues get involved in developing/starting this? New repository? 4. Would the community be interested in a .Net version of the Pact broker?

Hi @heymega. 1. I?m not sure it is complete, however it is a state where it could be used 2. No work has been done to get v3 into .NET yet 3. Your best bet is to take a look at https://github.com/pact-foundation/pact-net/issues/162 and get a feel for what is required. From there you can fork the repo and go from there. 4. I personally don?t think there would be a huge amount of value here. It would be a lot of work to get feature parity with the ruby one.

@raido.letterbox Support for custom SSL certs has been added in `2.4.3`

@neil - I'm looking at the version 2 implementation of the `IPactProvider.ServiceProvider` and notices that you can no longer pass in your own `HttpClient` and I believe you could in version 1. What was the reasoning behind this? I thought it was quite useful being able to pass in a `HttpClient` as part of the `TestServer`.

Is any example publishing to pact-broker for .net?

@antonios.klimis Check out the Github Repository... https://github.com/pact-foundation/pact-net#publishing-pacts-to-a-broker

Thx @heymega

@heymega Yeah that was a nice feature, however unfortunately when we moved to using the ruby standalone core we had to get rid of it as the ruby process takes care of sending the http requests.

Unfortunately that was one of the tradeoffs for getting version 2 support

Ahh that's a shame. We've can't run them on cloud agents in Azure Devops (vsts) as part of our build pipeline and have seen port clashes :disappointed:

Any strategy on how to output the whole error stack on state setup stage? At the moment I get `Failure/Error: set_up_provider_state interaction.provider_state, options[:consumer]` which is not very helpful.

has joined #pact-net

Hey @antonios.klimis. Did this error occur when running a verification? What were the provider state details of the pact file?

has joined #pact-net

can any one help me how to run can-i-deploy script ? i have downloaded the zip file and running the below command in my bash but i am getting error, what i am doing wrong *https://github.com/pact-foundation/pact_broker-client#can-i-deploy* my plan was to run can-i-deploy from C# code but before that i am running through curl but facing issue, any help is appreciated curl pact-broker.bat can-i-deploy --pacticipant clientpact --version 1.0.1.6 --broker-base-url http://devas.company.com

@thirumal.net I don?t think you want to run `curl pact-broker.bat`, it should probably just be `pact-broker.bat`

@neil - Thank you very much for your reply. i am able to run. just want to say thanks again for your valuable time for adding code in .net for pactNet which i am using for my proof of concepts

No problems. Thanks for your comment!

*How to Add Provider Side Tag to Pact Broker* ? i am able to run the provider verification successfully and publish the result to pact broker but not sure how to attach tag to pact broker from provider side ?

I don?t think you can. AFAIK you push a tag from a consumer PoV which is attached to the version. This question might be better in #pact-broker though

Thank you @neil

has joined #pact-net

Hi what's your thoughts, plans and timeline on creating new .net core implementation of pact free of ruby stuff? I'm currently working on such a thing and wondering if I should continue

We encourage people to get involved in using the FFI bindings from the rust implementation, rather than rolling your own.

Trying to keep multiple impls in line and rolling out features is very difficult otherwise.

but is rust implementation fully ready?

Do you have plans to make new .net implementation yourself? Maybe you are already 1 step from finishing it and it doesn't make sense for me to do anything

As Beth said, we would like to move to the rust impl using FFI bindings. The .NET repo previously had a native implementation, but it was a pain keep feature parity with the other Pact libraries, so we moved to the shared ruby core.

We haven?t done any work moving to rust, so if you?d like to take charge of moving from the ruby core to rust, that would be awesome! As far as I know the rust core is ready to go.

has joined #pact-net

Thanks Neil, good to know. I'll take a look what I can do with it.

hi guys, has anyone tried storing the pact file in the azure blob so that provider can read from there?

I personally haven?t tried it however, it?s definitely possible. You?d probably need to write some code to download the file locally and then just pass the verifier that path to the local file.

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

please refer this link, it might help since we can't generate pact files for multiple providers at same time

You can?t generate multiple pact files using the same provider mock, however you can run multiple provider mocks at the same time to generate multiple pact files. The only caveat is that they need to run on the different ports.

Hi there I had a question on the actual writing of the consumer side tests

Following the examples I implemented few tests in the format as described in the samples here

where we describe our expectation from the Producer service in the form like this

this api here doesn't have lot of properties, but in case if we have do

I found myself looking at the producer service's sdk

and actually got tempted to use the sdk models instead of defining them by hand here

is there a recommendation or catch to use this approach?

You can try it - what might bite you is that sometimes a domain model doesn't map exactly to the JSON.

Also, you'd be adding in attributes you don't necessarily care about. For contract testing to work at it's best, the consumer only defines what they care about.

This means that unused fields are free to change, and the provider knows who is using them.

yes that is one key difference

thanks Beth as always for your prompt help and response on my queries

:thumbsup::skin-tone-3:

Can I ask you one more question? :slightly_smiling_face: I was looking for pactnet examples, is this still the best resource https://github.com/pact-foundation/pact-net

or are there any other resources that we can refer?

I actually remember reading about using some format in order to deal with date fields which are auto generated, but I couldn't find it in above examples

I'm not the the pact-net maintainer, so I'm not sure.

@neil may be able to help you.

Are you talking about matchers?

Thanks Beth I will ping him.

Please don't PM him! He'll see this here.

oh I see.

Yes I happened to run into a consumer side test that involves dates and I was looking for example how producer side tests will match the dates where they are autogenerated on the producer side

Actually thanks for pointing to the right term I should have been searching for "matcher" I can now look it up better

:thumbsup::skin-tone-3:

I will try that but in the mean time @neil if you have a good resource please let me know

Thanks Beth as always!

@vikassd2012 The readme just contains a simple example. Probably best to have a look at the samples in the repo for a more complete example. Is this what you are after? https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs#L290

Hey @neil thanks for the example, this is exactly what I was looking for. Sorry I missed it earlier.

has joined #pact-net

Hi. I am new to contract testing and trying to create a POC for our http://ASP.NET WebApi application. I've been following the code example in your PactNet repo. I've been able to create working Consumer tests, but I'm having a bit of trouble creating the Provider test. We have a Global.asax.cs which starts the Provider application like this: public class WebApiApplication : System.Web.HttpApplication { protected void Application_Start() { Common.NetworkingHelper.ConfigHttpTlsLevel(); DependencyConfig.Configure(GlobalConfiguration.Configuration); WebApiConfig.Register(GlobalConfiguration.Configuration); FilterConfig.RegisterGlobalFilters(GlobalConfiguration.Configuration.Filters); RouteConfig.RegisterRoutes(RouteTable.Routes); GlobalConfiguration.Configuration.Formatters.Add(new System.Net.Http.Formatting.XmlMediaTypeFormatter()); } } But the example code in PactNet uses OWIN Hosting to start the application. I'm not sure how to reconcide the difference. Can you provide some helpful documentation that will help. An example code would also be very useful.

Hi @sthan. Unfortunately I don?t have any examples. The trick is that you need a way to start/run your web api programatically, once you have that hook, you should be able to get the Pact provider tests working. I?m assuming you run your app in IIS. Maybe there is a way to programatically trigger your api to run in IISExpress or something like that?

has joined #pact-net

I'm trying to hunt down some info on how to test a provider that is implemented as a webhook, but my google-fu is struggling and I haven't been able to find any info that isn't related to configuring webhooks in the pact-broker. The provider that I'm trying to test is a webhook. I would like to define a pact that expects an initial response for a given request from the consumer, but then also expects a callback from the provider that we're testing. Is testing webhooks possible with Pact, or is there some way to accomplish the test with multiple tools?

@bockus Yep it?s possible, basically your provider becomes a consumer for the webhook callback part. So effectively both parties in the interaction are consumers and providers. Does that make sense?

You then end up with two seperate pacts

ah, thanks @neil. Is there a way to tie those two pacts together as a type of sequence or something. I'm just wondering how I would verify that the consumer turned provider is receiving a callback as part of the initial test for the webhook.

I solved this problem by copying the Dependency registration inside the OWIN's TestStartup. Something like this: public void Configuration(IAppBuilder app) { HttpConfiguration config = new HttpConfiguration(); DependencyConfig.Configure(config); WebApiConfig.Register(config); FilterConfig.RegisterGlobalFilters(config); RouteConfig.RegisterRoutes(RouteTable.Routes); GlobalConfiguration.Configuration.Formatters.Add(new System.Net.Http.Formatting.XmlMediaTypeFormatter()); app.UseWebApi(config); }

Nah there isn?t any way to tie them together. Without full context about your use case, it?s tricky to give advice, however I don?t really think that kind of sequencing should be part of the contract test.

All the examples I've seen so far is where the Consumer creates a test that specifies the validity of the RESPONSE contract. The Provider runs the test to validate that assumption made by the Consumer. But when the Consumer makes a POST call where it sends some body in the REQUEST. How do I verify that body also conforms to to the contract? If you can point me to the right document, or example code, I would appreciate it.

Here?s an example for the POST scenario https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs#L125 Basically the provider test will send the exact POST request (with the body) at your provider and presumably if your provider did not understand the request body or it was incorrect, then it would return a response (maybe a 400 status) to indicate this to the consumer (and fail the Pact provider verification).

@neil Thanks for the reply. But perhaps, I should have been more specific with my question. What I'm trying to verify is the details of the contract sent to the provider. In the example, you sent me, POST call is made with request body with fields: eventid, timestampe, and eventType. Let's say that the only valid value for the eventType was "DetailsView" and "ListView". If this was a GET RESPONSE, we could do something like this in Consumer Test: eventType = Match.Regex("DetailsView", "(DetailsView|ListView)") But this is a POST REQUEST. I'm not sure how we can do this. My best guess is: In Provider test, we ask for the request body from IPactVerifier and examine the eventType to make sure it conforms to the regex. But looking at IPactVerifier, I don't see a way to get the request body. So, I was wondering if there was another way to get that data or if there is some other mechanism in place to verify this.

I'm trying to write a test for a provider that takes an image file in the body of a POST request, but I'm struggling to get that pact generated with the mock service. @neil, are you aware of any examples that build a ProviderServiceRequest with multipart/form-data content? This curl request is an example of the type of request I'm trying to test: `curl -X POST "https://example.com/save/file" -H "accept: application/octet-stream" -H "Content-Type: multipart/form-data" -F "fileToSave=@image.TIF;type=image/tiff"`

Nah I don?t have an example for this. Traditionally we only support JSON, however if the ruby standalone support it we could support it as well.

@bethskurrie Is this supported in the ruby standalone?

I can't remember!

I remember doing something for it. Let me have a look.

So, yes. It's a bit inelegant, but it works.

You need to use matchers on the headers because the boundaries will be dynamically generated.

if you follow the same pattern using the .net dsl, it should Just Work TM.

There's some in built logic to detect the dynamic form boundaries in the body, and do the matching so that your expected data will match your actual data even though the boundaries are different.

Thanks @bethskurrie!

You can use the matchers in the request bodies as well, so in the case of `eventType` like the example, you could do `eventType = Match.Regex("DetailsView", "(DetailsView|ListView)")`. What this would do is ensure that the consumer code only sends a request with eventType set to `DetailsView` or `ListView`. If it sent a request with eventType set to `Blah`, the request would not match any registered interactions in the mock provider, and the consumer test would fail.

Is this what you are after?

Thanks for your help @bethskurrie and @neil! I was able to make some progress by building the body of the expected request like you did in the linked example. Since the data being sent is an image, I'm hitting the same encoding error mentioned here: https://github.com/pact-foundation/pact-python/issues/97. Any ideas on how to work around that if I still want the provider to verify a pact where the request payload includes the bytes of an image?

@neil. Thanks again for the response. However, the solution you mentioned was a bit unexpected. My original question was based on an assumption I had in my head: Whoever receives the data (contract) is the one who is coming up with the validation logic (eg: Match.Regex(?DetailsView?, ?(DetailsView|ListView)?)). In a standard GET request, the Consumer receives data from the Provider. So it makes sense that the Consumer comes up with the validation logic and Provider provides the data to be validated. But in a POST request, the Consumer provides the data and Provider receives the data. Which means that Provider has to come up with the validation logic. Bottom line is this: As a Provider I want to make sure that the Consumer is sending me the right type of data (in the correct format) in a POST request. In your last example, Consumer is the one coming up with both the data and the validation logic. This was the reason why I asked if it was possible to get the Request body from the PactVerifier so that I can verify the data and format on the Provider side.

This is hard to answer as I don?t know your exact scenario. It?s probably better to think of it as: on the consumer side setting up a mock of the provider. You want to emulate what the consumer actually can send, and how the provider responds in those circumstances. If you?re testing a scenario that is generally not possible for the consumer to send, then my example above is the right approach. This makes sense if you?re just trying to check regression, for example if someone renames one of the `eventType` values. Suddenly your mock provider (which emulates your real provider) won?t be able to respond.

However if it?s completely valid for your consumer to send any `eventType` value, and it?s up to the provider to tell the consumer when the request is valid, then it should be a different approach. Your provider should return a response which indicates why the request is invalid, which can be verified in the response part of the consumer side of the contract.

In this case the provider is coming up with the validation logic, however the validation logic lives in your actual prod deployed provider code.

To directly answer > Bottom line is this: As a Provider I want to make sure that the Consumer is sending me the right type of data (in the correct format) in a POST request This logic should actually live in your provider, irrespective of Pact or not. If a consumer is calling you with the wrong type of data (in the incorrect format), you should tell them that by sending a response that is not 2xx, for example a 400 Bad Request.

If I wanted to contribute to pact-net, especially when it comes to support for the pact spec 3.0, how would I go about that?

Which part of the v3 spec are you interested in?

The first part of v3 spec we are trying to get in is Pact Message support. You can have a look at the PR comments https://github.com/pact-foundation/pact-net/pull/175 and https://github.com/pact-foundation/pact-net/issues/162. The PR is a placeholder and we are actually working on the `message-pact` branch. There is a TODO.txt file in the root of that branch, which has roughly what?s remaining. Help with any of those items would be great.

Alternatively it would be good to work out what is additionally required to get full v3 support after pact message is merged in.

Some background: I'm currently working on a big project where we want to test the interactions between multiple .net and java services with contracts (both http and message based). For this project it would be great I we could get pact-net fully compatible with pact-jvm as soon as possible. I'll start by looking at the TODO.

@neil Sorry for the late response. I've been putting out fires at work (not literally). But your last point makes total sense. The provider application should be responding with appropriate error message appropriate to the incorrect data in the POST request. Thanks for clearing things up.

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hi, do you have any example on how to write provider test for aws lambda service? I found this page but it is only for consumer test https://dius.com.au/2018/10/01/contract-testing-serverless-and-asynchronous-applications-part-2/

Hi Franklin, I think the pact message functionality for .net is still on a branch as it's not complete.

has joined #pact-net

Yeah the pact message code currently lives on the `message-pact` branch

I see. Thanks @matt.fellows and @neil

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hi, we are trying to run a pact verification against a response whose content is `text/csv`. We are getting an encoding error: Encoding::UndefinedConversionError: "\xC3" from ASCII-8BIT to UTF-8 Is csv content supported by pact-net or it it only json and form data that is supported?

To be honest, I have never tried with `text/csv`. I probably depends on if the ruby standalone supports it, which I am not sure.

@bethskurrie Do you know if the ruby standalone supports `text/csv`?

has joined #pact-net

Hi, I'm trying to work out a simple pact against a logging API. I's a REST API the I'm suppose to be able to POST a string value. I'm able to do it from already running application and in postman, but for some reason it want do it in pact using this interaction description. I'm receiving a response status 400.

I?m not sure if this is why, but it appears you are marking the request body as `application/json` and sending a plain text non json body.

has joined #pact-net

hi, I understand in PactJS 6.x.x there is something called GraphQLInteraction to help creating the expectations when trying to perform contract testing against a GraphQL endpoint. I'm kind of new with the whole Contract Testing topic so excuse me if I'm asking trivial or "already answered" questions. But I'm trying to perform the same on our .Net environment but haven't found an example as clear as I found it here http://blog.pact.io/2018/07/24/contract-testing-a-graphql-api/ Will really appreciate any guidance on this, I find my self in loops of readings saying it is possible with the current PactNet but without an example I could adapt to our environment. Thanks.

@dperez Hey. That?s new to me about PactJS. Nah the .NET implementation does not have any graphql interaction DSL.

As the article mentions though, you could construct a GraphQL request using the standard DSL. You?d just need to know the exact JSON that GraphQL is sending and replicate it.

@neil thanks for the reply. Will use the standard DSL then. Regards.

Hello, I was asking a couple of months ago about message support in pact-net. It's a requirement in my company for the adoption of Pact for our .NET Core microservices and I wanted to how the development on it was going, and if any help was needed.

I believe someone is working on it at the moment.

Have a look at the PRs in the pact net repo.

There is an old December one still open about this, but I understand the work is currently being done outside of it in a separate branch.

@neil do you knoe what the current status is of the Pact net message impl? I thought I saw some discussion on it recently. More recently than December.

has joined #pact-net

Yeah some people are using it from the `message-pact` branch and fixing some issues that are arising. There is a TODO.txt file with the known remaining bits. @iruben91 Feel free to take a look at that and see if there is anything you want to help with. I haven?t had any time lately to tick these off, house renos are taking up all my free time.

If the current pact-message branch does what you need, you can build your own package from that branch.

This thread will show you how https://pact-foundation.slack.com/archives/C5F4KFKR8/p1559190383002900

has joined #pact-net

has joined #pact-net

hey guys, please, review pr above ^^ thanks

Hi all, was wondering if anyone has any advice on how best to handle the PactNet.<OS> nuget packages depending on the target environment a build pipeline might be using eg Ubuntu for a Docker build pipeline or Windows when running locally etc Looked into condition nuget package references but that seems to be configurable only for the solution config. Thank you in advance

You can install both in your project and PactNet will pick which one it needs to use at runtime

has joined #pact-net

Hi guys, can I have a simple example for provider in C#?

Sure. Have you seen https://github.com/pact-foundation/pact-net/tree/master/Samples/EventApi

thanks

Hi Neil, does it show how to publish the pact file to the pact broker?

hi all, first at all, thanks for being so open and collaborative to questions in this channel. And sorry for the long post but I need to explain our code base the best I can, this is particularly about the message-pact branch. Now, we started playing with the message-pact branch about a month ago, and I know this is work in progress which I would love to collaborate back with our findings so far. But before that, I want to make sure I understand the "concepts" behind this branch. Currently we have microservices grouped by domains. We version our services by domain, not by single available operation inside the domain. We deliver a nuget package to our producers like: Builder.Microservices.1.0.0.0.nupkg containing all the possible messages the domain is expected to receive (among other commodity methods to interact with our messaging bus). If one of those message changes then a new package is created. (I know, not the best but a long history) So I want to test all the interactions *with my domain*. Some notes: a) Isn't an open public microservice, we know by hand who are our message producers. b) We use widely in our projects BDD, in this case SpecFlow. Just as a side note that might affect design decisions. With all that mind, 1. On the microservice consumer side I want to create a contract for *each producer* (is this correct?) 2. I have the following expected messages: CreateCorporation, CreateBrand, CreateDivision. Will all the expected messages be part of a single pact file? Or each needs to have it's own pact file? I was expecting to have all the possible messages of my domain in one single file per producer.

Hi @dperez I haven?t personally tried with SpecFlow, but there shouldn?t be anything technically stopping that from working. 1. You create a contract (Pact file) for each consumer/producer pair. 2. Same as above, you?ll likely want a contract for each consumers usage of those produced events. For example one consumer might only use a single field in CreateCorporation and not consume the CreateBrand event at all, so the contract for that consumer/producer pair would only contain the used fields and events.

Hi @neil Thanks for the reply. The issue we are having now, is how to create some kind of protection from the Consumer side by the time of updating a contract to know before hand what producers we are affecting. Just uploading a new contract to the broker isn't enough since each producer must run their tests against the new contract to notify the broker if it passed or not. We had the idea that the broker worked in a different way, basically that the producers upload their side of the history (their version of the contract) and the broker performed a comparison based on that. Without running each producer tests is there some way to figure out if a producer that is compatible with my version 1.0.0 will be also compatible with the new version 2.0.0 I haven't even released?

I think I have understood the problem, however I?m not 100% sure. An event consumer can only use data that is made available by an event producer. If a consumer decides it needs something new, it?s their job to negotiate this with the producer team. Pact doesn?t remove the need for documenting and communication between teams. If there was some communication breakdown and the event consumers started using a field the producer had not made available, then the producers verification build should fail. The broker has a webhook feature which allows it to send a http request to a predetermined endpoint whenever a new consumer contract is pushed. This can be used to trigger the producer verification automatically. Once both the consumer and producer verifications pass, then the change can be deployed. If it fails, it generally signals that a conversation hasn?t happened. This is also worth having a read https://dius.com.au/2017/09/22/contract-testing-serverless-and-asynchronous-applications/

Thanks a lot. This is a really good reading, and the point about the webhooks I think is the missing piece we were looking for.

Nice one!

Hi in pact-js, there is an github example to show how to use Match based on arrays?

is there one for http://pact.net?

@mui_ume Looks like the MinType matcher will work https://github.com/pact-foundation/pact-net/blob/message-pact/PactNet/Matchers/Type/MinTypeMatcher.cs Seems to do the eachLike() ArrayLike reg ex type from what I can tell

Yep that?s the one you want

There isn?t an explicit example of that matcher in the samples, but it does have other matchers. Match.Type is the closest to Match.MinType https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs#L289

can pact net support messaging comes from websockets?

hi @matt.fellows and @bethskurrie is there a setting to match the body in case insensitive

the pact file is pascal case and the return response is in lower cases

Do you mean in the actual request / response from provider? No

That seems... Odd

has joined #pact-net

nm, it's something to do with the object deserialisation in the consumer service. we have updated the contract in consumer in order to match with the provider

ah ok

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hello! When will 'Multiple provider states' feature be supported for .net?

has joined #pact-net

I was trying to set PactDir in consumer side where pact files generated but it always create in d:\pacts directory? Is this a bug? Another issue coming is how provider will get all pact files for specific provider? It can be multiple consumers using one provider?

Without seeing your config, I can?t really help

You create a provider test for each of the consumers.

public ConsumerPactClassFixture() { // Using Spec version 2.0.0 more details at https://goo.gl/UrBSRc PactBuilder = new PactBuilder(); PactBuilder.ServiceConsumer("Event Client") .HasPactWith("Event Server"); MockProviderService = PactBuilder.MockService(MockServerPort); var pactConfig = new PactConfig { SpecificationVersion = "2.0.0", PactDir = @"D:\pacts1\", LogDir = @"D:\pacts1\pact_logs" }; }

When will pactbroker publishing and verifications for pactnet support?

You need to initialise the `PactBuilder` with the config object. See https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/ConsumerEventApiPact.cs#L19

It is already. See the readme. https://github.com/pact-foundation/pact-net#publishing-pacts-to-a-broker https://github.com/pact-foundation/pact-net#publishing-provider-verification-results-to-a-broker

Thanks

How to install pact broker in azure devops? I do not want to use docker image. Want to do installation manually?

Please reply as it is urgent

Also one more query that i am trying to access dius server to publish pacts but i am getting error ? no connection made because target machine refuses? We are using proxy so could not connect this url directly. How to use proxy ?

Sorry I can?t help you with Azure devops, I?ve never used it before

Maybe post the dius server pact broker question in #pact-broker

has joined #pact-net

Ok i will post

Any luck with my second query on proxy issue?

has joined #pact-net

has joined #pact-net

That?s the one I suggested posting in #pact-broker

I have a scenario in which consumer is using one of the wcf based service so how will i implement the solution using PACT?

@mohindroo.deepak - i don't think pactnet supports non jason services

In one of the scenario, one of the consumer service A Get method calls another http service B internally. I want to test the service A here. i will make the mock http server for Service B but problem here is how will i redirect service A call to new mock server?

In your samples, it is passing new mock server in get url. Which is not possible in my case. Obviously we can not make all api methods have url parameter.

Are you referring to this part of the sample? https://github.com/pact-foundation/pact-net/blob/e0532b782e673acb6d1d16b96b2cbb72c07a3075/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs#L51 It is actually good practice to allow every API client you want to test to have at least the base url injected.

Yes. My consumer app is dotnet core which internally call the provider. In the test case, i cannot pass the mock url which i have made. How to implement pact mock server here?

You should really implement pact tests as unit tests in the consumer app. If that's not possible and the consumer app is a black box to you you must be able to inject the url somehow, there's no way around that.

You are saying that i should run consumer tests before deploying the consumer service? Which i normally do in unit testing as well. In unit testing as well, i normally mock the dependencies and run my tests. Another point is that if i have 3 dependencies used in one of the POST function in consumer api then do i need to pass 3 different urls in the POST method parameters? Is this a good practice to change consumer api methods for the testing purpose only?

Let me explain my case in detail: I have few tests which runs after the consumer service deployed and that is using restsharp to call the consumer api methods. In some of the methods, there is a call to 2 different providers to fetch data. I want to use pact to mock those 2 providers and run my tests and generate pact file. So below queries - 1) how to inject these urls for providers? 2) if i lets say inject those urls at the time of deployment of consumer service, then if i use pact mock code in the test case, will that work?

3) on the provider side, pact tests will run on real provider service deployed?

To answer your first question: yes, I'm saying that you should run your consumer tests before deploying the consumer service. Second: you say you want to "use pact to mock those 2 providers". This is imo a bad practice, you should only use pact for what it's meant for: generating and verifying contracts. If you want to mock services to run functional integration tests I would recommend using another mocking tool. It's possible to do with pact but it just gets confusing. To answer your queries: 1) you probably want to get base urls from some kind of config anyway. I normally wouldn't hard code them anyway, so using configuration would be the way to go. 2) Probably, but again, I wouldn't recommend it. 3) On the provider side the same advice applies: please don't run the tests against the actual deployed service, but run them as unit tests against a self-hosted version of the service in some test-specific configuration. You only want to test the interface (i.e. your controller) so you need to be able to mock everything behind that.

For 3) i have seen your sample and it runs against the actual provider service

It will of course hit the actual provider *code*, but it will not be "deployed" as such. https://github.com/pact-foundation/pact-net/blob/e0532b782e673acb6d1d16b96b2cbb72c07a3075/Samples/EventApi/Provider.Api.Web.Tests/EventAPITests.cs#L34

But I guess we mean the same thing.

Yeah but startup function of main service have azure keyvaults being used so how this will work on build agent

How we can self host the app service in build pipeline

Its slightly difficult

One more query that in provider test, we are mentioning consumer name but if we have lot of consumers with different names and multiple consumers break then how will get info about the same.

Are you there

??

There is an issue coming when i add pactnet.windows nuget because of long path in ruby at thebtime of building the project. Any solution for this?

I am trying to run the pact verify code in dotnet and it works with pact file but not working with url. Giving some ruby files error? Need some help or code snippet to do that.

Does the url return a pact file json body? Does it require auth?

Well when i run url on browser, it shows json content and this does not require authentication.

Are you using the broker or something else?

I am using broker

Consumer part working perfectly fine with broker

You don't need to mention the consumer name in the provider test. You only need to make sure that you support the provider states supplied by each consumer.

Also what are these providestatemiddleware codebase

Ok i need to understand provider states

There is standard piece of code for providerstate middleware. What is the purpose of this? Is this fixed code need to use?

I doesn't have to be middleware, it can also be a controller. What basically happens is that the Pact Mock Consumer will perform a request to "/provider-states" with the providerState part of the contract. You need to expose this "/provider-states" endpoint somehow to be able to set up the correct data to be able to comply with the actual test.

I did not get you fully here. Data is sometimes dynamic and data which is store in pact file might not work aftre few days

So is there a way to bypass data check ? If we just want to validate properties name only? Also do you have some samples with provider states url on provider side

?

So now i am able to run the pact file on provider side

But still getting some error

When the actual data doesn't matter you should use Matching Rules. You should really start by reading the official documentation (http://pact.io). It's really good.

Do you have some samples around the customized provide states? Which explain my usecase?

Sorry I can?t help without more details

That works now

Thanks

Now i have one question regarding the pact provider states. I do not want to validate the data in pact file. Just want to compare the json parameterss names. Is this possible?

Any sample with pactnet with matchers?

I have found this

Matchers are probably what you are after. Have a look at the samples in the repo https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs

Anything `Match.` is a matcher

Sounds like `Match.Type` is probably what you are after

I am getting one issue that when provider tries to validate the pact file, it is failing that due to below issue 1) Verifying a pact between DummyConsumer and DummyProvider Given There is data Invalid SSI with current client id with GET /api/provider?clientid=222293222 returns a response which has a matching body Failure/Error: expect(response_body).to match_term expected_response_body, diff_options Actual: {"id":2,"name":"Test","clientId":2222222,"currencyCode":"DKK","countryCode":"CI"} Diff -------------------------------------- Key: - is expected + is actual Matching keys and values are not shown { - "Id": 2, - "Name": "Test", - "ClientId": 2222222, - "CurrencyCode": "DKK", - "CountryCode": "CI" } Description of differences -------------------------------------- * Could not find key "Id" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "Name" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "ClientId" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "CurrencyCode" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "CountryCode" (keys present are: id, name, clientId, currencyCode, countryCode) at $ This email may contain confidential and/or privileged information. If you are not the intended recipient - or have received this email by mistake - please notify the sender immediately and destroy the email. Any unauthorised copying, disclosure and/or distribution of the contents and/or attachments in this email is strictly prohibited. Email transmission security and error-free delivery cannot be guaranteed as information could be intercepted, corrupted, destroyed, delayed, incomplete and/or contain malware (virus). The sender of this email, therefore, does not accept liability for any errors and/or omissions in the contents of this message, which may arise as a result of email transmission.

I can see one difference in actual: properties first character in lower case which is done by pact automatically? Dont know why

This can be the cause i guess

One more question about amqp messaging. My use case is that i am sending lot of messages to azure service bus/kafka so how will i handle those contracts?

@mohindroo.deepak - you can fix this issue by using JsonProperty . here is the example code which solves your issue public class ClassName { [JsonProperty(PropertyName = "id")] public string Id{ get; set; } [JsonProperty(PropertyName = "name")] public string Name{ get; set; } }

i have faced the same issue when i am doing POC on pactnet . above code helped me to fix the issue

Thanks :blush:

Any solution for this

When i use matcher.type for the whole body, it is not showing in the pact file generated?

Am i missed anything

Sorry this part works. Pls ignore

I have made the cicd pipeline for consumer And upload pact files to broker but how will i validate this to provider side? Do i need to trigger build cicd pipeline of provider side as contract tests is one of the task in provider build pipeline?

The Pact Broker has a webhook feature, which allows you to trigger a provider verification when a consumer pact is uploaded

But that verification will trigger provider side build?

Or it will just verify with latest pact version ?

@mohindroo.deepak - webhook will trigger the provider side build and provider side unit test case should fetch the latest version from pact broker and verify it. it depends which pact file you are getting from pact broker .

[Fact] public void VerfiyPacts () { string pactBrokerUrl = @"http:// .com/pacts/provider/Test_Provider/consumer/Test_Consumer/latest"; //Arrange const string serviceUri = "http://localhost:62809"; var config = new PactVerifierConfig { Outputters = new List<IOutput> { new XUnitOutput(_output) }, PublishVerificationResults=true, ProviderVersion= providerAPIVersion }; using (WebApp.Start<TestStartup>(serviceUri)) { //Act / Assert IPactVerifier pactVerifier = new PactVerifier(config); pactVerifier .ProviderState($"{serviceUri}/provider-states") .ServiceProvider("service", serviceUri) .HonoursPactWith("client") .PactUri(pactBrokerUrl) .Verify(); } }

I am getting one issue that interaction not matching Consumer application has some dto which gets converted into json parameters and pass in httpresponse. When i am trying this in Pact so it fails and does not match. How to pass multiple parameters in Query? I also have dto which i need to pass here. Any help?

has joined #pact-net

How to pass multiple parameters in query

Can anybody help urgently

How POST works with pact? How can i pass parameters and get response object?

You can see at line 124 an example of a post for teh consumer side

But in this case, you mentioned response object in body?

In my case, there is parameters as well and there is response object. When i see consumer interaction in log file, it did not show response json in body. Rather it is showing request json in body

??

Post carries request data in body so if we have some reponse as well then why pact is not writing anywhere?

I am getting one issue if i use Body in providerservicerequest then it breaks the execution and error pact exited due to *arguementexception*

what do you have in your .WillRespondWith()?

I am getting one issue if i use Body in providerservicerequest then it breaks the execution and error pact exited due to *arguementexception*

Body is dynamic, not sure what problem it is you're having, check against the above see if you're set up is ok. https://github.com/pact-foundation/pact-net#3-write-your-test

I am using body in providerservicerequest

Then i got this issue. Execution breaks

Otherwise it works fine

It works now. I have not added content type header. But strange part is that execution should not break

In order for us to help, we need much more context about your specific issue. For example, if you?re getting an argument exception, there should be some info about which argument is causing the issue.

Hi, I have a question. Can I save an Enum name in the iteration or only be save the number? Sorry for my English.

1) I have a query on implementation of provider side- consumer pact will be published everytime when consumer ci build will trigger. When provider build will run, will they check all versions of consumer pacts everytime? Consumer pacts which has been verified in previous provider verification, will they also be picked up?

2) if provider will release api version 2 and trigger ci build, how will we stop validating consumer pacts? Whats the best practice to implement?

3) i am also confused about data management here. Set of data being used by consumer can be failed when provider will validate. As provider hitting actual api so that wrong data can change the response type. Any suggestions on that?

Really appreciate if somebody can answer

You should be able to just cast the enum to an int. So `int thing = (int) MyEnum.Member`

You choose what version of the pact you want to run by specifying the PactUri.

I don?t really understand the question. Why would you want to stop validating the consumer pacts because version 2 has been released?

You can either use matchers, provider state or both on the consumer side. Provider states give the provider a chance to setup the consumers data prior to running the verification. See https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Provider.Api.Web.Tests/EventAPITests.cs#L39 and https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Provider.Api.Web.Tests/ProviderStateMiddleware.cs#L24

I did not get this. In provider verification, i have written the code to get all pacts under this provider and build so it always update all pact which has been verified before

I mean that if there is a change in provider api contract and release new version of api but pact validate code picks old consumers which has older versions so it gets fail?

Thanks. i am aware of the matchers but there is a different case here E.g. in provider function, there is a condition if. Clientid not exists then return response code BadRequest. Client data is in input parameter. Consumer Pact is expecting OK status

Provide side code is generic and you normally call all pacts from specific branch. Whats the best practice to fetch pacts in provider build?

There can be some business logic on provider side and if data is wrong then response code can be changed due to that verification failed.

has joined #pact-net

You either need to use provider states to set up the right data, or you need to use middleware to change the response so that it matches the IDs that you have.

Here's some example middleware that sets a header https://github.com/pact-foundation/pact-provider-verifier/blob/master/spec/support/custom_middleware.rb

Unfortunately it needs to be written in ruby.

I believe there is a config option to set the middleware file @neil?

You actually want to verify the "old consumers" because that's what allows you to ensure you have backwards compatibility.

You should use tags.

Unfortunately there is no custom middleware in Pact-Net land, however a lot of the .NET web servers support middleware, which you could load when starting the provider for verification.

But it might possible that new property gets introduced in return json so it is fine for tthe consumers but pact verification will fail.

In that scenario the verification should not fail as the consumers have not specified the field in their contract

Ok

Sometimes pact mock server interactions not clear if something goes wrong at the time of development. Then no log file generated, no pact file in that case. I need to change the port number and then it start working.

Yeah that?s due to Pact-Net not being able to kill the ruby mock server process as it died unexpectedly

If you search for the ruby process and kill it manually, you shouldn?t need to change port

Ok. But i think that problem will not occur in cicd pipeline

On the build agents

Yeah it shouldn?t

It?s one of those ones, I wish I could fix, but unfortunately when the app domain crashes, I have no hooks to terminate other processes

See https://github.com/pact-foundation/pact-net#known-issues

@mohindroo.deepak - you can manually kill the mock service. at the end of the unit test case you can write like this public void KillByPort(int port) { var processes = GetAllProcesses(); // This gets all running process if (processes.Any(p => p.Port == port)) try { Process.GetProcessById(processes.First(p => p.Port == port).PID).Kill(); } catch (Exception ex) { Console.WriteLine(ex.Message); } else { Console.WriteLine("No process to kill!"); } }

i am calling this method in end of my unit test case. let me know if you want complete code snippet

There is a flag in the cli that lets you specify a Ruby file. But if you can load middleware in the net app, that would be much nicer.

:+1:

I need to know more on PactNet support on consumer sending messages to Azure Service bus and on the side, another service is receiving. Who will be the provider here? I guess message receiver should be provider. And how can we ensure contract testing here?

I'm not sure if the message pact support in .net is complete yet.

``` Consumer: An application that makes use of the functionality or data from another application to do its job. For applications that use HTTP, the consumer is always the application that initiates the HTTP request (eg. the web front end), regardless of the direction of data flow. For applications that use queues, the consumer is the application that reads the message from the queue. Provider: An application (often called a service) that provides functionality or data for other applications to use, often via an API. For applications that use HTTP, the provider is the application that returns the response. For applications that use queues, the provider (also called producer) is the application that writes the messages to the queue. ```

But if the test process is terminates unexpectedly, then I don?t think that code will run.

Nah it?s not complete yet, but it is somewhat functional on the `message-pact` branch

Any ETA when it will be officially launched?

Some of the people working on it have gone quite and I haven?t had the time to get it done. So no ETA at the moment

The above thread will tell you have to create a nuget package for that branch

From our experience, and from our requirements I can say it have done the job. The branch at least for us have worked very good, some minor adjustments but mostly all works pretty well

@neil - Thank you and Nice to see response from you. i am wondering , it is fine to kill the process in Dispose method of XUnit right ? or before starting the unittest case we can make sure mock service is not runnung on same port

@neil - Hi Could you please look into my scenario and suggest me if my thinking is correct ? i am doing analysis on pact implementation for C++ projects but there is no out of box support for C++ from pact community . as a work around i am creating one library in .NET which included PactNet and pact-win32( Ruby stand alone libraries for windows) . i am thinking to provide this .net library to C++ team so that they can include this .net library and call necessary methods like below (my understanding is calling C# library methods from C++ is possible ) 1) Start Mock Provider service 2) Clear Interactions 3) Register interactions 4) Consumer Code under test 4) Verify interactions 5) Stop Mock Provider Service 6) Publish the pact to pact broker Do you think this is good idea to implement pact where there is no language support ? Thanks in Advance,

This would mean that from your C++ code, you're calling C# code which calls the Ruby code by launching the process. You can skip the middleman by launching the Ruby process yourself. Also do note that while Ruby executable is the current approach for Pact, there is a work in progress on creating a Rust library (https://github.com/pact-foundation/pact-reference) which will eventually replace the Ruby executable.

Oh Great. I will try in next few days and will share the feedback

Yeah agree with the above. I definitely wouldn?t be using the .NET library here. Either use the Ruby standalone directly in a similar way to how .NET does it, or even better use FFI bindings for Rust. The downside of the Rust implementation is that I don?t think currently any of the Pact libraries use it. That being said, I?m told that it?s ready to go.

@dperez Any adjustments that you can share in a PR?

hi, nothing yet, all the adjustment we have done are for specific business requirement

Ah no worries :thumbsup:

has joined #pact-net

Hey guys, Ive just started hooking up PACT for a few new microservices im working on - I have the consumer/provider tests running locally and just in the process of setting up TeamCity CI. In TeamCity, it seems to be going fine with the consumer side, in that I can build and publish to the pact broker - however on the Provider build, I am having difficulty spinning up the Webhost which fails pact verification. In the PACT broker, it gives me: `Cannot assign requested address - connect(2) for "localhost" port 9223 (Errno::EADDRNOTAVAIL)` Im developing in .net core and typically I would use a TestServer, however looking around at samples and various comments online it is stated that you need to use a proper Webhost for the PactVerifier to work? I've pretty much got a solution similar to this: https://github.com/tdshipley/pact-workshop-dotnet-core-v1/blob/master/CompletedSolution/Provider/tests/ProviderApiTests.cs#L26 Has anyone had any luck hooking this up in TeamCity? As I mentioned Ive always used TestServer, so wondering whats missing to get it going..

Running the build step inside a docker container seems to have resolved my issue - all good :slightly_smiling_face:

How can i use can-i-deploy with PactNet consumer ? How to use in ci/cd pipeline?

Any example somewhere? How can i download can-i-download utility?

Any idea how to resolve this

I cant put jsonproperty

I am getting one issue that when provider tries to validate the pact file, it is failing that due to below issue 1) Verifying a pact between DummyConsumer and DummyProvider Given There is data Invalid SSI with current client id with GET /api/provider?clientid=222293222 returns a response which has a matching body Failure/Error: expect(response_body).to match_term expected_response_body, diff_options Actual: {"id":2,"name":"Test","clientId":2222222,"currencyCode":"DKK","countryCode":"CI"} Diff -------------------------------------- Key: - is expected + is actual Matching keys and values are not shown { - "Id": 2, - "Name": "Test", - "ClientId": 2222222, - "CurrencyCode": "DKK", - "CountryCode": "CI" } Description of differences -------------------------------------- * Could not find key "Id" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "Name" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "ClientId" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "CurrencyCode" (keys present are: id, name, clientId, currencyCode, countryCode) at $ * Could not find key "CountryCode" (keys present are: id, name, clientId, currencyCode, countryCode) at $ This email may contain confidential and/or privileged information. If you are not the intended recipient - or have received this email by mistake - please notify the sender immediately and destroy the email. Any unauthorised copying, disclosure and/or distribution of the contents and/or attachments in this email is strictly prohibited. Email transmission security and error-free delivery cannot be guaranteed as information could be intercepted, corrupted, destroyed, delayed, incomplete and/or contain malware (virus). The sender of this email, therefore, does not accept liability for any errors and/or omissions in the contents of this message, which may arise as a result of email transmission.

Any help on this?

This is Urgent

I think you'll work it out if you read the error message properly.

`Could not find key "CountryCode" (keys present are: id, name, clientId, currencyCode, countryCode) at $`

But countryCode key is available

First letter is not caps

Check case maybe?

Is the comparison case sensitive?

Correct

How to check case in provider side

Consumer has already send the pacts to broker

Either the code or the pact is wrong. One of them needs to change.

On the consumer side, json generated from dto and that is having first letter is in Caps

Is there any way to skip this on provider side?

No - it appears to be an integration bug.

This is exactly the kind of thing contract testing is supposed to identify.

One side expects capitalised names, the other expects ones with a lower case. They will not work correctly together in real life.

On the consumer side, i am using body=Match.Type(dto)

Dto properties is in caps

Well change the code.

Urgent for you maybe. Please do not pass on urgency to others. We're here to help, but we aren't paid to help you. We do it because we love it

I think when pact generated, it change the first letter to small

No, the pact expects an upper case. The provider is returning a lower case.

Sorry about that but it looks like an issue

As I said early, you need to change either the consumer+pact, or the provider, so that they match.

This is all the advice I can give now unfortunately.

There is no bug with the Pact code.

There is a dto which is having 2 properties and both are strings. First letter is in caps. When we generate the pact using consumer side code. It change the first letter to small.

Sorry Pls ignore my last line as consumer is generating the right properties. Only provider side makes issue

I just check swagger also showing json object properties first letter in smaller case

I got the problem. That is related to newtonsoft json which converts the property name first character.

I am getting NilClass as value of property is coming null. I do not want to compare the data so i used Match.Type but seems it does not work with null values

Any help on this?

If a property can be null you should leave it out of the contract entirely.

No but i just do not want to compare data under that property but would like to check the contract.

What do you mean by "check the contract?"

Yeah what @bart.schotten said. If you don?t care about the property, don?t include it in the interaction on the consumer test

Actual provider service does not have that data. So consumer pact is generating response body with some fake data which is not available on provider side. But property in response body needs to be compared.

Thats why i used Match.Type

On the consumer side

Yeah, that doesn't make any sense. If the provider does not have that property it has no business being in the contract.

Provider do have this property. But value is coming null because consumer is sending some fake data here

So in provider code, they fetch the data on the basis of some clientid

And that clientid is fake in the consumer pact

Of course, but that's why you have provider states, so that the provider can set up realistic test data to return

If the provider returns a value in reality, but not during the pact test, the provider test is not set up correctly.

In provider states, setting up test data means mocking of data?

Or you are saying, generating that client setup in database so that when actual provider call happens, it works accordingly?

You can do it either by setting up data in the database, or by mocking a repository or service, that's up to the provider to decide. As long as it does hit the actual controller/endpoint.

Adding in database not feasible in my case. Will provider middleware support Mocking of provider service?

I mean to say here that verifier code hits the actual controller end point. If i would like to mock the provider service or response data, how can i do that?

This question is not really related to Pact anymore. You're basically asking how you can test an API.

Not really. I am actually looking for some felxibility on provider side code to skip data validation

Like i have another example. There is a dto Which has 2 properties IsOK book and ErrorText string In case if IsOk come true then errortext set to null in the provider code. Consumer also send it as null in the property. But when provider runs, it marks as Nil

How can i compare null data in one of the consumer pact property with provider side Nil

Nil is NilClass

You don't. You should define two interactions in your contract. - Interaction 1: in which IsOK is true and ErrorText is not present (so not null, but really non-existent) - Interaction 2: IsOK is false and ErrorText has a string value.

In interaction 1, i cannot remove that errortext property. As there is dto desiarilize in the code to make json.

Interaction 2 works fine here

If i give c# null in json in consumer side

Will that work when provider will run

Compare the pact

Let me try this

That works :blush:

That is working now. Thanks

I am trying to get all pacts for particular provider using /latest

But i am getting mesage that deprecated

I am trying to get all pacts for particular provider using /latest But i am getting mesage that deprecated

Hi, all I see that in latest PactNet.Windows nuget there is no Version property for PactOption. Could somebody suggest any other code that I can use to generate it?

I only found way to generate it manually string version = DateTime.UtcNow.ToString(_pactOption.CustomDateTimeFormat, (IFormatProvider) CultureInfo.InvariantCulture) + (object) Guid.NewGuid();

I was trying to use PACT_Description environment variable for individual interaction verification for consumer pact. But it does not update on the broker. There are 3 interactions in 1 consumer pact file. I am trying to execute one by one in 3 different tests on provider side. Pact broker do not updated in this.

Anyone who tried environment variable for individual pact verification?

@??

Another issue i am facing is that i have created 2 consumers for 1 provider and when we run provider verification . Should validate all consumers pactVerifier. Serviceprovider(providername, provideruri) .pacturi(url) .verify

sorry, posted by mistake

I was trying to use PACT_Description environment variable for individual interaction verification for consumer pact. But it does not update on the broker. There are 3 interactions in 1 consumer pact file. I am trying to execute one by one in 3 different tests on provider side. Pact broker do not updated in this. Any help on this?

You can only publish verification results if you verify the entire pact.

@mohindroo.deepak ^^

Hi

has joined #pact-net

has joined #pact-net

hi @neil hope everything is good on your end. I noticed there's being some releases and was wondering if we could have those merged into the messaging branch ?

Yep sure can, will sort that out tomorrow.

thanks a lot

@dperez master is now merged into message-pact

thanks!

has joined #pact-net

Hey guys, had 2 questions on Pactnet

1. When I call PactBuilder.Build(); function to save the contract json file on my local I am noticing the casing of the file saved changes

For example my consumer and producer names that I am passing are

EventService and WorkService respectively

but the function saves the file in format eventservice-workservice.json

I am also using pactbroker after above step

to publish the pacts and there the name casing matches as per my input

what I am doing wrong? How I can get the local file casing to match as per my inputs and also PactBroker?

The 2nd question

I don't think you can

Pretty sure the code performs a downcase on it. Why does it matter?

You should just be able to publish the directory, and not care about the names.

Thanks Beth for your response, is it a convention to use downcase for service names?

You can make your own convention

the file name should be irrelevant - the contents of the file will contain the names with cases as you specified.

yes you are correct the content of the file has the right name casing

it mattered because I accidentally tried to query the pactbroker api with lower case

and got a 404

as expected

my concern was if I did this mistake other people in my team could do it too

so I was curious for the reasons

To be honest, you're the first person who has ever raised it.

I don't think it will be a major issue.

You'll have many bigger issues :stuck_out_tongue:

yes thats what I am trying to solve right now :slightly_smiling_face:

so I will leave the naming as is for now, hoping I am the only one who ran into it

my 2nd question was regarding pact broker api

I was trying to get interactions

using api

it only returned me 1 interaction

but I have 2 interactions

how I can get all ?

Have you published the version with 2 interactions?

Go to the broker UI and look at the matrix page

Its the icon with a little grid

oh

it only shows 1

but my local file has 2

well, it hasn't been published then

I will take a look not sure why it only published one

thanks Beth

np

How can we start pact mock server in some other server apart from localhost?

We are running main service in cloud and test running in onprem server

So localhost will not work

Any suggestions how to implement that

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hello, I am having trouble creating a PACT for a particular request using the .Net implementation of PACT. More specifically I am attempting to test a GraphQL POST request against a host server on this IP (http://52.188.176.147:4000). When running my dotnet test command, I am getting the following exception: ```System.Exception: 'There was a problem connecting to Provider API - {MYAPI}' - HttpRequestException: Response status code does not indicate success: 500 (Internal Server Error )``` I am able to successfully test my ConsumerAPIClient which contains the following code: ```using Newtonsoft.Json; using RA; using System; using System.Collections.Generic; using http://System.Net; using http://System.Net.Http; using http://System.Net.Http.Headers; using System.Text; using System.Threading.Tasks; namespace Consumer { public static class ConsumerApiClient { static public async Task<HttpResponseMessage> LocationQuery(string baseUri) { using (var client = new HttpClient { BaseAddress = new Uri(baseUri) }) { try { string json = JsonConvert.SerializeObject(new { query = "\n{\n locations {\n displayName\n }\n}" }); var content = new StringContent(json.ToString(), Encoding.UTF8, "application/json"); var response = await client.PostAsync($"{baseUri}", content); response.EnsureSuccessStatusCode(); return response; } catch (Exception ConnectionEx) { throw new Exception("There was a problem connecting to Provider API - LocationQuery.", ConnectionEx); } } } } }``` Here is my consumer test class:

``` using Xunit; using PactNet.Mocks.MockHttpService; using PactNet.Mocks.MockHttpService.Models; using Consumer; using System.Collections.Generic; using PactNet.Matchers; using RA; namespace tests { public class ConsumerPactTests : IClassFixture<ConsumerPactClassFixture> { private IMockProviderService _mockProviderService; private string _mockProviderServiceBaseUri; private int _mockProviderServiceBasePort; public ConsumerPactTests(ConsumerPactClassFixture fixture) { _mockProviderService = fixture.MockProviderService; _mockProviderService.ClearInteractions(); //NOTE: Clears any previously registered interactions before the test is run _mockProviderServiceBaseUri = fixture.MockProviderServiceBaseUri; // _mockProviderServiceBaseUri = "http://52.188.176.147:4000/"; } [Fact] public void LocationQuery() { // Arrange _mockProviderService.Given("There is no data") .UponReceiving("A valid POST request to validate location GraphQL") .With(new ProviderServiceRequest { Method = http://HttpVerb.Post, Path = "", //Query = "", Headers = new Dictionary<string, object> { { "Content-Type", "application/json" } }, Body = new { query = "\n{\n locations {\n displayName\n }\n}" } }) .WillRespondWith(new ProviderServiceResponse { Status = 200, Headers = new Dictionary<string, object> { { "Content-Type", "application/json; charset=utf-8" } }, Body = new { data = (new { locations = Match.MinType(new { displayName = "" }, 2) }) } }); // Act var result = ConsumerApiClient.LocationQuery(_mockProviderServiceBaseUri).GetAwaiter().GetResult(); var resultBodyText = result.Content.ReadAsStringAsync().GetAwaiter().GetResult().ToString(); ; // Assert Assert.Contains("data", resultBodyText); } } }``` I would appreciate your help on this issue.

@neil regarding the issue above, I also changed my MockProviderService's configs to use the IP address binding settings, but still has no luck. Here is my ConsumerPactClassFixture.cs: ```using PactNet; using PactNet.Mocks.MockHttpService; using PactNet.Models; using System; using Xunit; namespace tests { // This class is responsible for setting up a shared // mock server for Pact used by all the tests. // XUnit can use a Class Fixture for this. // See: https://goo.gl/hSq4nv public class ConsumerPactClassFixture : IDisposable { public IPactBuilder PactBuilder { get; private set; } public IMockProviderService MockProviderService { get; private set; } public int MockServerPort { get { return 9222; } } public string MockProviderServiceBaseUri { get { return String.Format("http://localhost:{0}", MockServerPort); } } public ConsumerPactClassFixture() { // Using Spec version 2.0.0 more details at https://goo.gl/UrBSRc var pactConfig = new PactConfig { SpecificationVersion = "2.0.0", PactDir = @"..\..\..\..\..\pacts", LogDir = @".\pact_logs" }; PactBuilder = new PactBuilder(pactConfig); PactBuilder.ServiceConsumer("TaxonomyConsumer") .HasPactWith("TaxonomyProvider"); MockProviderService = PactBuilder.MockService(MockServerPort, host: IPAddress.Any); } //teardown #region IDisposable Support private bool disposedValue = false; // To detect redundant calls protected virtual void Dispose(bool disposing) { if (!disposedValue) { if (disposing) { // This will save the pact file once finished. PactBuilder.Build(); } disposedValue = true; } } // This code added to correctly implement the disposable pattern. public void Dispose() { // Do not change this code. Put cleanup code in Dispose(bool disposing) above. Dispose(true); } #endregion } }```

Looks like you?re getting a 500 response from the server, so it?s likely something to do with provider not knowing how to handle the request it has been sent.

`Body = new { query = "\n{\n locations {\n displayName\n }\n}" }` seems a little odd to me

It means you?ll be sending the following json to the server ```{ "query": "\n{\n locations {\n displayName\n }\n}" }```

It feels like you might be trying to send ```{ "query": { locations { displayName: "" } } }```

Also the string inside query isn?t valid json

That's correct. However, when I execute dotnet run in consumer proj using the same string, I am getting the correct response and payload. I also tested the same string in Postman and was able to get the desired response. I have a feeling the error is related to how I am passing the host server's ip address and port to the mockserver

Is your provider verification code using the correct pact file? I?d build a very simple test provider api, which just logs the request that has been sent by pact, to ensure it?s as expected. Without any of the provider verification code and the provider api, I can?t really help much here.

hi team, I would like to try .net core for messaging-pact. anyone could suggest where I can start? I see that we have this branch "https://github.com/pact-foundation/pact-net/tree/message-pact" how can I start with that?

There was a repo somewhere

BTW, hi!

I think there was another repo, as well as that branch

@neil might remember. Unfortunately we have the free slack, and so the messages about that might have dropped off our storage.

do you meant you guys are not actively working on that at the moment?

@bethskurrie is this the repo https://github.com/Mattersight/pact-net-messages

Nope

It's been a long while since anyone touched it

hi @franklin.huynh take a look at this thread for a message implementation https://pact-foundation.slack.com/archives/C5F4KFKR8/p1559190383002900

I noticed the thread is now archived, I'm able to see it but probably because I starred it, let me know if you have some problem reaching it.

hi @dperez I cannot see the message. Could you share it to me?

@franklin.huynh hope it helps.

thanks @dperez I'll try follow the thread . many thanks

we are actually using the branch mentioned in the thread for our contract testing with our messaging infraestructure and have to say, it does the job

Hello there, I am attempting to run my consumer and provider tests in an Azure Pipeline using an ubuntu agent with Azure tasks. I am able to run the tests fine in my local machine on Windows. However, whenever I switch my PactNet Nuget package to Linux64, and build/run my tests projects, I encounter a failure in my provider test with the following message: ```Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command Version : 2.164.0 Author : Microsoft Corporation Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/build/dotnet-core-cli ============================================================================== /usr/bin/dotnet test /home/vsts/work/1/s/pact/Provider/tests --logger trx --results-directory /home/vsts/work/_temp Test run for /home/vsts/work/1/s/pact/Provider/tests/bin/Debug/net472/tests.dll(.NETFramework,Version=v4.7.2) Microsoft (R) Test Execution Command Line Tool Version 16.3.0 Copyright (c) Microsoft Corporation. All rights reserved. Starting test execution, please wait... A total of 1 test files matched the specified pattern. [http://xUnit.net 00:00:02.69] tests.ProviderApiTests.EnsureProviderApiHonoursPactWithConsumer [FAIL] X tests.ProviderApiTests.EnsureProviderApiHonoursPactWithConsumer [274ms] Error Message: System.TypeInitializationException : The type initializer for 'PactNet.Constants' threw an exception. ---- System.UriFormatException : Invalid URI: The format of the URI could not be determined. Stack Trace: at PactNet.PactVerifier+<>c.<.ctor>b__47_0 (PactNet.Core.PactVerifierHostConfig hostConfig) [0x00000] in <24e08d8a874b4357a3f70f66dbe375e6>:0 at PactNet.PactVerifier.Verify (System.String description, System.String providerState) [0x0010b] in <24e08d8a874b4357a3f70f66dbe375e6>:0 at tests.ProviderApiTests.EnsureProviderApiHonoursPactWithConsumer () [0x000a4] in <37a774785b2a4ef3a32cbac10560f0ad>:0 at (wrapper managed-to-native) System.Reflection.RuntimeMethodInfo.InternalInvoke(System.Reflection.RuntimeMethodInfo,object,object[],System.Exception&) at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x0006a] in <c453bf849bb84e719dbec0475e99db95>:0 ----- Inner Stack Trace ----- at System.Uri.CreateThis (System.String uri, System.Boolean dontEscape, System.UriKind uriKind) [0x0007b] in <4d8f95b7df544b3fa1a27dda924b4424>:0 at System.Uri..ctor (System.String uriString) [0x00014] in <4d8f95b7df544b3fa1a27dda924b4424>:0 at PactNet.Constants..cctor () [0x0001e] in <24e08d8a874b4357a3f70f66dbe375e6>:0 ``` All my tasks (Nuget restore, dotnet run/test) are running fine, and my consumer tests are passing. One thing to note, not sure if relevant, is the fact that I targeted different frameworks for my consumer proj (netcoreapp 2.1) and provider proj (net 472). Below is my code for my provider test class: ``` using System; using System.Collections.Generic; using PactNet; using PactNet.Infrastructure.Outputters; using Xunit; using Xunit.Abstractions; using Microsoft.Owin.Hosting; using tests.XUnitHelpers; namespace tests { public class ProviderApiTests: IDisposable { private string _serviceUri { get; } private string _providerUri { get; } //private string _pactServiceUri { get; } private readonly ITestOutputHelper _output; public ProviderApiTests(ITestOutputHelper output) { _output = output; _providerUri = "http://52.142.17.145:4000"; _serviceUri = "http://localhost:9001"; } [Fact] public void EnsureProviderApiHonoursPactWithConsumer() { //Arrange const string serviceUri = "http://localhost:9001"; // var buildNumber = Environment.GetEnvironmentVariable("BUILD_NUMBER"); DateTime utcDate = DateTime.UtcNow; var buildNumber = utcDate.ToString(); var config = new PactVerifierConfig { ProviderVersion = !string.IsNullOrEmpty(buildNumber) ? buildNumber : null, //NOTE: This is required for this feature to work PublishVerificationResults = !string.IsNullOrEmpty(buildNumber), Outputters = new List<IOutput> { new XUnitOutput(_output) } }; using (WebApp.Start<TestStartup>(serviceUri)) { //Act / Assert IPactVerifier pactVerifier = new PactVerifier(config); pactVerifier.ProviderState($"{serviceUri}/provider-states") .ServiceProvider("TaxonomyGraphQLProvider", _providerUri) .HonoursPactWith("TaxonomyGraphQLConsumer") // .PactUri(@"..\..\..\..\..\pacts\taxonomygraphqlconsumer-taxonomygraphqlprovider.json") .PactUri("https://blnmanagermobilesvc.pact.dius.com.au/pacts/provider/TaxonomyGraphQLProvider/consumer/TaxonomyGraphQLConsumer/latest", new PactUriOptions("MyAPIKey")) .Verify(); } } public virtual void Dispose() { } } }``` Please advise if you need further details to look at this. I am hoping this is a simple formatting issue that I missing given the fact that I've been staring at this for hours! Thank you much!!

hi @dperez can I know which OS you are running the test? I did publish the nuget package (PactNet) and it ran successfully on Windows. However, it failed on mac saying it cannot find the . I think I need to publish the PactNet.OSX package. do you know how can I publish it?

hi, correct, I'm running the Windows one only. Let me try to find the instructions about that one. Or probably @matt.fellows or @bethskurrie can give us a hint how to build that one.

@bethskurrie @neil @matt.fellows would you be able to advice?

FYI @dperez I just realised in your archived message has instruction how to publish the package including OSX, Linux. I will follow through

Sorry, I know less than nothing about dot net! @neil is the expert (sorry to bug you Neil!)

it happened to me as well. What version of pact you're using?

probably same with this https://github.com/pact-foundation/pact-net/issues/231

if you're using 2.5.0, try converting to 2.4.8

I think I'm progressing with the publish the OSX package. But this issue is blocking me https://github.com/pact-foundation/pact-net/issues/231

@franklin.huynh if you give me a docker container to reproduce the issue, I'll investigate.

Thank you so much! That worked!

Hello, I am unable to serialize hyphenated JSON keys in the body content of my consumer tests. This is needed as some of the keys returned in the response payload follow the "xx-id" format. Please see example (application-id) below: ``` [Fact] public void RejectTimesheetWithoutAComment() { // Arange _mockProviderService.Given("There is no data") .UponReceiving("Timesheet to reject without an approver's comments") .With(new ProviderServiceRequest { Method = http://HttpVerb.Post, Path = "/approvals/actions/reject/4faf9285-78d4-4c09-b836-1cd48c393ed2", Query = "", Headers = new Dictionary<string, object> { { "Authorization", "Bearer TOKEN"}, {"Content-Type", "application/json; charset=utf-8" } }, Body = new { } }) .WillRespondWith(new ProviderServiceResponse { Status = 400, Headers = new Dictionary<string, object> { { "Content-Type", "application/json; charset=utf-8" } }, Body = Match.Type(new { application-id = new { comments = new { location = "body", param = "comments", msg = "Comments are required" } }}) }); // Act var result = ConsumerApiClient.RejectTimesheetWithoutComment(_mockProviderServiceBaseUri).GetAwaiter().GetResult(); var resultBodyText = result.Content.ReadAsStringAsync().GetAwaiter().GetResult().ToString(); // Assert Assert.Contains("errors", resultBodyText); }``` When attempting to build my test projects, VS fails the build due to the hyphen being part of the key. Is there a way around this? Please advise

Is this a Pact specific issue? Seems like you need a way to specific a key as a string in .NET

There seems to be no way for me to manipulate the key when it is inside the body section of the test. Even if I attempt to serialize it outside the method, it does not appear to recognize keys. Am I missing something?

Might have to wait for someone else here, I'm not experienced .NET

It's not a Pact specific issue. I don't think .NET supports hyphens in identifiers https://stackoverflow.com/questions/5771577/can-you-have-a-property-name-containing-a-dash/5771598

No .NET doesn?t support that. If you want to do that you?ll need to create a .NET class which with http://Json.net JsonProperty attributes (https://www.newtonsoft.com/json/help/html/JsonPropertyName.htm) to represent that object rather than using a dynamic/anonymous object.

has joined #pact-net

has joined #pact-net

has joined #pact-net

Hi everyone, i am trying to tag my provider with my branchName, to publish into the broker, but it is not working i am doing this: i don't now if this is well implemented?

Is it not getting sent to the broker at all? Are there errors? Are you running on Windows, Linux or OSX?

has joined #pact-net

Hi, i was wondering if i can save all interactions to json file without executing any endpoint tests?

has joined #pact-net

Hi guys, maybe you can help me. Trying to find out if there a way I can validate fields name & type and not actual values?

Hello, i am running on windows when i review the broker it has the provider version correctly however tag is not been added, the variable is already returning a value so i do´nt know if i am missing something when try to add the tag to the provider.

You can try Match.Type ```_mockProviderService.Given(...) .With(...) .WillRespondWith(new ProviderServiceResponse { Status = 200, Body = new { eventType = Match.Type("Test") } });```

https://github.com/pact-foundation/pact-net/blob/master/Samples/EventApi/Consumer.Tests/EventsApiConsumerTests.cs has many examples

thanks! that worked perfect

I have another question and I will explain it with an example. I have a request to get session (generated guid) and I'm using this session for the next request to get some data from the provider. I want to test both requests, is there a way to "save" the response from the first request and use it on the second request?

You want to research the topic called ?provider states?

Each interaction should be able to be tested in isolation - you?re talking about a _functional_ test (that relies on state and a sequence of pre-conditions to be setup)

Pact takes a different approach

So in your example, you should have two tests: 1. Get (or generate?) a session ID 2. Do something to /some/API _given_ session ID 1234 exists (the ?given? bit, is the state)

OK, Thanks, I will look into that

Hi there, I have encoding problem. Seems like when reading the pact file (provider side) somehow encoding of some character messed-up, This is the error I received: Expected "\u256B\u00C9\u256B\u00D6\u256B\u00DC \u256B\u00C9\u256B\u00E1\u256B\u00F9\u256B\u00E1\u256B\u00F2 \u256B\u00D6\u256B\u00A2\u256B\u00F2\u256B\u00A3\u256B\u00D6\u256B\u00A5 \u256B\u00A3\u256B\u00F3\u256B\u00FB\u256B\u00F2\u256B\u00BF \u256B\u00A3\u256B\u00DC?" *but got* "\u05D0\u05D9\u05DA \u05D0\u05E0\u05D7\u05E0\u05D5 \u05D9\u05DB\u05D5\u05DC\u05D9\u05DD \u05DC\u05E2\u05D6\u05D5\u05E8 \u05DC\u05DA?" at $.result.unavailableSelfServiceActions[1].selfServiceActions[3].selfServiceActionFields[1].fieldTitle The 'Expected' unicode characters aren't in the actual pact file (the character int the pact file are actually unicode characters after 'but got' ) How can I fix that?

Can you send a simple repro repo, which demonstrates the issue?

Hello again, our company is in the early stages of implementing PACT. We currently have a running provider service in Azure that returns data of a certain user using a JWT stored in the QA database. I've been having some discussions with some of the devs and QAs, and few of them are under the impression that PACT mocks the provider in both consumer and provider tests. Their theory is that PACT validates the contract against a mocked instance of the provider service that way dependencies are handled without impacting the tests. Is that the case, or does PACT replay the interactions recorded in contract against the running service? Finally, are there any guidelines around mocking databases with the http://a.NET implementation of PACT? I am leaning towards using provider-states to inject data in the QA database before running the provider test, but some of the dev have a preference of staging up a database prior to a test run. Thank you for your help!

> Is that the case, or does PACT replay the interactions recorded in contract against the running service?

Yes

Thank you Beth. I've been using PACT for the past couple of months, and I've created some training around running tests against a live provider. However, that point was challenged by some of the team member based on some the examples they found online. Thank you for confirming. Per your knowledge, are there use cases where provider is a mocked instance?

No - that would defeat the purpose

Could you find me this misleading documentation?

> I am leaning towards using provider-states to inject data in the QA database before running the provider test, but some of the dev have a preference of staging up a database prior to a test run.

You want your pact verification tests to be able to be run on a local developer machine.

That way you can know if you're going to break any consumers *before* you commit.

If you use a shared QA database, you would (I imagine) have to commit first, which would slow down your feedback loop.

I am just trying to wrap my head around testing the service in the local box. How would that play into implementing contract testing in the pipeline? My theory was to commit and deploy changes, then run a canary/A-B type of test in the pipeline where you have multiple instances of the running service (stage vs prod). If stage pipeline fails, it rolls back to most recent stable version of master. Today our company is operating with a monolithic on-premise architecture that is being changed to a distributed model. This means we will be, initially, bringing in developed services from the legacy app to Azure and run contract testing for each service in isolation. Is that something you recommend, or do you have other thoughts in mind?

Contract tests aside, can you run unit tests in this thing? Can you run those on your local development machine?

If so, then you should definitely try to run your contract tests as part of that cycle. Running against a deployed environment is possible but adds some of the downsides of interested tests (in particular, the possibility of non-determinism)

Hi everyone, there is a way to retrieve the tags available in the pactBroker, according to the consumer tag versions, to build the url to verify in the provider side? i am working with pact-net in my provider side

something like "pactbroker.consumerVersionTags" but i want to verify it in my code building in the CI process, without dependency with the webhook broker

has joined #pact-net

I'm seeing similar behaviour on OSX too. It versions the verification result with the ProviderVersion but does not add any tags

Thanks for extra info, I?ll have a look into it.

So it turns out that option was added accidentally. If you want to use ProviderTags, you set it by using `.PactBroker` rather than `.PactUri` when configuring the broker url and auth settings ect. The `PactBroker` method will give you the option to supply `providerVersionTags` .

The readme has some more info https://github.com/pact-foundation/pact-net#2-tell-the-provider-it-needs-to-honour-the-pact

I?ll remove the `ProviderTags` from `PactVerifierConfig` now

Yup, using `.PactBroker` and giving the `providerVersionTags` works. Thanks! Any specific reason why we're wrapping the tags in quotes? Using `pactPublisher.PublishToBroker` on the consumer side tags it with the string without any wrapper in quotes

Also, using the consumerVersionTags don't seem to be applied. I have a consumer contract with `test` tag but running the verification doesn't verify the contract ```.PactBroker("<<pactBrokerUri>>", consumerVersionTags: new List<string> { "test" });```

But removing the consumerVersionTags verifies the contract with `master` tag

Yes, when testing locally, a localhost is running in the a developer's box where we can test all the changes before deployment. Does that mean that we need to implement PACT as a manual step before merging? If that's the idea, then I am suspecting that we tag branch name on both provider and consumer sides, publish branch contract to broker, test branch provider against branch contract, merge branch contract into master contract , test branch provider against master contract, and then merge branch provider into master?

I wouldn't say as a "manual step" - it's all automatible. But yes something like you described is correct. There are a few pages about effective Pact setup on http://docs.pact.io that can help you think about it

It?s usually to handle spaces in the value and things like that

Any reason not to wrap in quotes?

Pretty sure I tested the consumer tags and it worked

Just tested it again and it worked for me. What PactNet version are you running? Maybe try updating to the latest if you haven?t already.

Yup, it's working for me now. Thanks! I was using 2.5.1 and updating to 2.5.2 worked :slightly_smiling_face:

has joined #pact-net

Hi All, I am new to CDCT and some help would be greatly appreciated, I use pactflow and able to publish the pact via my consumer code but for my provider i want to do the verification of that pact this fails on the PactVerifier last step , with the following error; /// PactNet.PactFailureException: 'Pact verification failed. See output for details. If the output is empty please provide a custom config.Outputters (IOutput) for your test framework, as we couldn't write to the console.' Help would greatly appreciated my code is as below; var comp= new PactClient(); /* //this is calling the api endpoint /pacts/provider/provider/consumer/Service_Consumer/latest to retrieve the pact file which works fine */ var pact= comp.GetPact(); var config = new PactVerifierConfig { Outputters = new List<IOutput> { new XUnitOutput(_output) }, ProviderVersion = "1.0.0", PublishVerificationResults = true, CustomHeaders = new Dictionary<string, string> { { "Authorization", "Bearer xxxxx" } }, }; IPactVerifier pactVerifier = newPactVerifier(config); pactVerifier.ServiceProvider("Service_Consumer", "https://dev-api-endpoint.com") .HonoursPactWith("contract") .PactBroker(pact.ResponseUri.AbsoluteUri) .Verify( description: "A request is made", providerState: "A GET request for getting titles is submitted");

What does the logs/output say? Without that info, I can?t tell what the problem is.

Is the value of `pact.ResponseUri.AbsoluteUri` the base Pactflow url?

Also I don?t understand why you need to do: ```var comp= new PactClient(); var pact= comp.GetPact();```

I think you want to checkout, the below line in the readme ```.PactBroker("http://pact-broker", uriOptions: new PactUriOptions("sometoken"), enablePending: true, consumerVersionTags: new List<string> { "master" }, providerVersionTags: new List<string> { "master" }, consumerVersionSelectors: new List<VersionTagSelector> { new VersionTagSelector("master", false, true) })```

Using: ```CustomHeaders = new Dictionary<string, string> { { "Authorization", "Bearer xxxxx" } }``` is not the way to specify your broker/pactflow token (if that?s what it is in your example)

yes the url was not correct that was the issue for the test not passing now it passes but now the issue is even though PactFlow dashboard should reflect the verification for some reason it is not.

i do it to call pactflow api to get the pact from the broker url and it returns be the published pact. i thought it wd make more sense for the provider test to find the pact first.

@neil I submitted the logs, compare to yesterday definitely it is better but now only problem i face is the dashboard does not reflect the verification and i do not see any errors

i believe it can not find any interactions as in the logs but normally it should have ??

in the pact file which is json, i see that there is an interactions section on there which is not empty

@dikili if you can copy the latest version of your code into a gist we can have a look.

@neil what happens to the stdout from the Ruby code? Does it get printed or saved anywhere? It should say that it's either published or not published the verification results.

Yeah that?s a fun one. Some test runners in .NET redirect stdout way from the console, that?s what the Outputters part of the PactVerifierConfig is.

Please use these channels rather than direct message, that way others can help and this can hopefully help others. Any logs should be formatted and any not useful or sensitive information removed/redacted.

Righto

if anyone is interested in joining the .NET team as a core maintainer, please reach out - we have a number of big items on our roadmap that will require significant investment and collaboration across the group. For example: v3.0, better messages support, gRPC/Protobufs and more. Pact has open many doors for the core team, we?d love to help open some for you too

@dperez

Hi @matt.fellows , @pbarrientos and myself we are highly interested to contribute to the team.

Amazing folks. I?ll tee up a chat

Cross posting from the protobuf channel: Just wanted to share that I finally managed to release my custom pact implementation with support for protobuf serialization. It?s compatible with the pact spec v2 (I.e. makes the specs tests green), and is available for .NET Standard 2.0 https://github.com/ChristianEder/impact The path I took allows to add custom serialization formats - such as protobuf - in addition to Json, and also to exchange the transport layer (out of the box, I support HTTP) at will. Pleased let me know what you think!

has joined #pact-net

has joined #pact-net

Hi there , I am beginner with Pact , I have been able to run consumer and provider tests provided at https://github.com/pact-foundation/pact-net. But I have question for the experts , when we test the provider APIs which interacts with and external component for example a SQL db , how do we deal with such scenario when running contract tests on local developer machine . As we do not deploy the services instead use self hosted routing .

Could not find relation 'pb:latest-provider-pacts' in resource at https://variantest.pact.dius.com.au/pacts/provider/Event%20API/consumer/Event%20API%20Consumer/latest-untagged (Pact::Hal::RelationNotFoundError)

Can anyone help on this ?

v

pactVerifier .ProviderState($"{serviceUri}/provider-states") .ServiceProvider("Event API", serviceUri) .HonoursPactWith("Event API Consumer") //.PactUri($"..{Path.DirectorySeparatorChar}..{Path.DirectorySeparatorChar}..{Path.DirectorySeparatorChar}..{Path.DirectorySeparatorChar}Consumer.Tests{Path.DirectorySeparatorChar}pacts{Path.DirectorySeparatorChar}event_api_consumer-event_api.json") .PactBroker("https://test.pact.dius.com.au/pacts/provider/Event%20API/consumer/Event%20API%20Consumer/latest-untagged", new PactUriOptions("rALSJLBCK;JDVBK")) .Verify();

Do you have a very very old version of the Pact Broker?

Oh, right, you're on Pactflow. Have a look at the resource.

Oh, I see.

You just need the base url of the Pact Broker

You're putting the pact url in.

You either give it the pact uri, which is the full url to the pact, or you give it the provider name and the base url of the Pact Broker, and it will fetch the pacts automatically for you.

thanks for the reply Beth , when I used PactURI the was passed but the verification status was not updated on Pactflow . I also tried setting up PublishVerificationResutls to true , but got an error . I am strill struggling to successfully use PactBroker even with just the baseuri , most of the time I am getting 301 status code . can you point me to some examples with .NET , where .Also how can I publish the tag and version for consumer while pushing Pact file to PactFlow ?

Siddharth, did the example I share with you the other day not work?

OH! I did not push, that would explain that

So sorry - please see this file: https://github.com/pactflow/pact-workshop-dotnet-core-v1/blob/master/CompletedSolution/Provider/tests/ProviderApiTests.cs#L57-L64

I also added notes to the readme :https://github.com/pactflow/pact-workshop-dotnet-core-v1#running-on-pactflow

I hope this clears things up

Thanks Matt , I was able to pus back the verification results using Pacturi by specifying ProviderVersikon in PactverifyerConfig . Above code and document also helps me . I am going to try my hands with webhook today and let you know if I have any questions , Can I delete the Pact file from pactflow as developer account supports only one pact file ?

It should support up to 5 contracts, but yes you can delete

the API supports it via a `DELETE`

we don?t yet have a UI option in the new style, but if you go to `use old UI` you can delete from there

thanks

has joined #pact-net

Hello, I was looking at the example code to setup the mock providers within the consumer unit tests and it makes me think if specific implementation of `ProviderServiceRequest` and `ProviderServiceResponse` would be useful to make the setup a little compact ? so that we could do something like ```_mockProviderService .Given("There is a something with id 'tester'") .UponReceiving("A GET request to retrieve the something") .With(new JsonGetRequest("/somethings/tester") .WillRespondWith(new JsonOkResponse { Body = new { id = "tester", firstName = "Totally", lastName = "Awesome" } );```

Hi everyone, someone can help me with this problem? The broker is already up because the test are verified, but when try to publish the verification result to the broker, the result the following message appears pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.2/lib/pact/provider/verification_results/publish.rb:103:in `publish_verification_results': Error returned from verification results publication 500 {"error"=>{"message"=>"An error has occurred. The details have been logged with the reference agMzWQbfmU", "reference"=>"agMzWQbfmU"}} (Pact::Provider::VerificationResults::PublicationError) i am using "PactNet.Linux.x64" Version="2.5.3" in a jenkins pipeline

has joined #pact-net

Hello, I am attempting to validate the following contract for a provider that returns an array of objects: using the eachLike matcher method: ```{ "consumer": { "name": "assignmentApolloGQL" }, "provider": { "name": "CWS" }, "interactions": [ { "description": "An existing assignment Id", "providerState": "default", "request": { "method": "POST", "path": "/EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses", "headers": { "Content-Type": "application/json;charset=utf-8" }, "body": { "skip": 0, "top": 10, "assignmentNumber": 4961 } }, "response": { "status": 200, "headers": { "Content-Type": "application/json" }, "body": [ { "friendlyId": "4961", "assignmentId": "a425c44e-868e-4bb4-b80e-ad64d1060011", "status": "Expired", "subStatus": "N/A", "approvalStatus": "Extension in Progress", "modifyDate": "0001-01-01T05:00:00Z", "clientName": "Foggy" } ], "matchingRules": { "$.body": { "min": 1 }, "$.body[*].*": { "match": "type" } } } } ], "metadata": { "pactSpecification": { "version": "2.0.0" } } }``` The payload that provider returns a payload that looks like this: `[`     `{`         `"friendlyId": "4961",`         `"assignmentId": "a425c44e-868e-4bb4-b80e-ad64d1060011",`         `"status": "Expired",`         `"subStatus": "Extension in Progress",`         `"approvalStatus": "HM Approval",`         `"modifyDate": "0001-01-01T05:00:00Z",`         `"clientName": "Foggy"`     `}` `]` However, when validating the provider I am getting the following error: `Failures:` `1) Verifying a pact between assignmentApolloGQL and CWS Given default An existing assignment Id with POST /EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses returns a response which has a matching body` `Failure/Error: let(:response_body) { parse_body_from_response(response) }` `JSON::ParserError:` `757: unexpected token at '???[{"friendlyId":"4961","assignmentId":"a425c44e-868e-4bb4-b80e-ad64d1060011","status":"Expired","subStatus":"Extension in Progress","approvalStatus":"HM Approval","modifyDate":"0001-01-01T05:00:00Z","clientName":"Foggy"}]'` `1 interaction, 1 failure` `Failed interactions:` `To re-run just this failing interaction, change the verify method to '.Verify(description: "An existing assignment Id", providerState: "default")'. Please do not check in this change! # An existing assignment id given default` `WARN: Cannot publish verification for assignmentApolloGQL as there is no link named pb:publish-verification-results in the pact JSON. If you are using a pact broker, please upgrade to version 2.0.0 or later.`

Also here is the log from the provider: ```I, [2020-04-30T19:44:30.265610 #19644] INFO -- : Running example 'Verifying a pact between assignmentApolloGQL and CWS Given default An existing assignment Id with POST /EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses returns a response which has status code 200' I, [2020-04-30T19:44:30.574623 #19644] INFO -- : Sending POST request to path: "/EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses" with headers: {"CONTENT_TYPE"=>"application/json;charset=utf-8", "HTTP_X_PACT_ORIGINAL_HEADER_NAMES"=>"Content-Type", "X_PACT_PROVIDER_STATES"=>[{"name"=>"default"}]}, see debug logs for body D, [2020-04-30T19:44:30.574623 #19644] DEBUG -- : body :{"skip":0,"top":10,"assignmentNumber":4961} I, [2020-04-30T19:44:35.295607 #19644] INFO -- : Received response with status: 200, headers: {my headers"}, see debug logs for body D, [2020-04-30T19:44:35.296614 #19644] DEBUG -- : body: [{"friendlyId":"4961","assignmentId":"a425c44e-868e-4bb4-b80e-ad64d1060011","status":"Expired","subStatus":"Extension in Progress","approvalStatus":"HM Approval","modifyDate":"0001-01-01T05:00:00Z","clientName":"Foggy"}]```

I can't see anything immediately wrong. You've got an array as a top level element, but that should be supported.

Can you try and reproduce it using this repository, so we can take a look at it? https://github.com/pact-foundation/pact-ruby-standalone-e2e-example

This is an example using the underlying engine that Pact Net uses.

That will help us identify where the issue lies.

maybe also check the headers that are coming back. I looked at your logs just there and saw ?my headers? - not sure if you edited it. Thtis being said, I?m pretty sure another issue would first show up

If you can cURL that endpoint and share the fully headers/response body, that would be useful

Hi Matt, I omitted the headers here is the full log: `I, [2020-04-30T20:14:22.866006 #40704] INFO -- : Running example 'Verifying a pact between assignmentApolloGQL and CWS Given default An existing assignment Id with POST /EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses returns a response which has status code 200'` `I, [2020-04-30T20:14:23.164009 #40704] INFO -- : Sending POST request to path: "/EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses" with headers: {"CONTENT_TYPE"=>"application/json;charset=utf-8", "HTTP_X_PACT_ORIGINAL_HEADER_NAMES"=>"Content-Type", "X_PACT_PROVIDER_STATES"=>[{"name"=>"default"}]}, see debug logs for body` `D, [2020-04-30T20:14:23.164009 #40704] DEBUG -- : body :{"skip":0,"top":10,"assignmentNumber":4961}` `I, [2020-04-30T20:14:27.620041 #40704] INFO -- : Received response with status: 200, headers: {"Date"=>"Fri, 01 May 2020 00:14:27 GMT", "Content-Type"=>"application/json", "Content-Length"=>"223", "Connection"=>"keep-alive", "Set-Cookie"=>"__cfduid=d4e63f8909d64d03ead55af65d25b03491588292066; expires=Sun, 31-May-20 00:14:26 GMT; path=/; domain=.http://beeline.com; HttpOnly; SameSite=Lax\n.BEEAUTH_qa059=4c04bcea-5a60-4663-891b-e76f2d652312; expires=Sun, 03-May-2020 00:14:27 GMT; path=/; secure; HttpOnly\na74qacl051=qaweb403.sfld; path=/; HttpOnly; Secure\n__cfruid=515b3ca5ba0b16ce5ab42e254ddf44ee65cf8261-1588292067; path=/; domain=.http://beeline.com; HttpOnly; Secure; SameSite=None", "Cache-Control"=>"private", "Strict-Transport-Security"=>"max-age=300; includeSubDomains; preload; always;", "Content-Security-Policy"=>"frame-ancestors *.http://beeline.com *.http://iqnavigator.com *.http://iqnavigator.eu *.http://beeline.to *.http://beelinetowork.io` `http://beeline.to` `http://beelinetowork.io` `https://beebot-bot-sales.azurewebsites.net` `https://beebot-bot-prod.azurewebsites.net` `https://beebot-bot-proj.azurewebsites.net` `https://beebot-bot-hfreg.azurewebsites.net` `https://beebot-bot-reg.azurewebsites.net` `https://beebot-bot-pct.azurewebsites.net` `https://beebot-bot-qa.azurewebsites.net` `https://beebot-bot-hfqa.azurewebsites.net` `https://cdn.botframework.com` `` `https://directline.botframework.com", "X-Xss-Protection"=>"1", "Totalserverpagetime"=>"569", "Cdnheader"=>"{\"AuthenticationDate\":\"2020-05-01T00:14:27.5297229Z\",\"AuthenticationType\":\"Auth0CwsLogin\",\"ImpersonationType\":\"Self\",\"UserName\":\"gmurray\",\"OrganizationType\":\"Beeline\",\"Organization\":null,\"ImpersonateeUserName\":null,\"ImpersonateeOrganizationType\":null,\"ImpersonateeOrganization\":null,\"CFRAY\":\"58c54d6a6ce7e3c2-DTW\"}", "X-Content-Type-Options"=>"nosniff", "X-Ua-Compatible"=>"IE=edge", "Accept-Ranges"=>"bytes", "Cf-Cache-Status"=>"DYNAMIC", "Expect-Ct"=>"max-age=604800, report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\"", "Server"=>"cloudflare", "Cf-Ray"=>"58c54d6a6ce7e3c2-ATL", "Cf-Request-Id"=>"026f2eb6830000e3c259184200000001"}, see debug logs for body` `D, [2020-04-30T20:14:27.620041 #40704] DEBUG -- : body: [{"friendlyId":"4961","assignmentId":"a425c44e-868e-4bb4-b80e-ad64d1060011","status":"Expired","subStatus":"Extension in Progress","approvalStatus":"HM Approval","modifyDate":"0001-01-01T05:00:00Z","clientName":"Foggy"}]`

has joined #pact-net

Hi Beth, I can certainly do that, my only concern is that I am passing a JWT as a custom header on the provider side, not sure if I'd be allowed to include it in my forked solution. Do you want me to fork it without the JWT?

yes, it shouldn't affect the repro.

the standalone example doesn't actually include any pact net code - it's doing the bare minimum to reproduce an issue.

it looks like the issue is in the body

Abdel - for future code posts, can you try using the triple backtick? That will format the code much better

in any case - it looks OK to my eyes

Sorry, if it helps: ```I, [2020-04-30T20:14:22.866006 #40704] INFO -- : Running example 'Verifying a pact between assignmentApolloGQL and CWS Given default An existing assignment Id with POST /EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses returns a response which has status code 200' I, [2020-04-30T20:14:23.164009 #40704] INFO -- : Sending POST request to path: "/EndPoints/Cloud/Assignment/AssignmentService.svc/RawJSON/GetAssignmentStatuses" with headers: {"CONTENT_TYPE"=>"application/json;charset=utf-8", "HTTP_X_PACT_ORIGINAL_HEADER_NAMES"=>"Content-Type", "X_PACT_PROVIDER_STATES"=>[{"name"=>"default"}]}, see debug logs for body D, [2020-04-30T20:14:23.164009 #40704] DEBUG -- : body :{"skip":0,"top":10,"assignmentNumber":4961} I, [2020-04-30T20:14:27.620041 #40704] INFO -- : Received response with status: 200, headers: {"Date"=>"Fri, 01 May 2020 00:14:27 GMT", "Content-Type"=>"application/json", "Content-Length"=>"223", "Connection"=>"keep-alive", "Set-Cookie"=>"__cfduid=d4e63f8909d64d03ead55af65d25b03491588292066; expires=Sun, 31-May-20 00:14:26 GMT; path=/; domain=.http://beeline.com; HttpOnly; SameSite=Lax\n.BEEAUTH_qa059=4c04bcea-5a60-4663-891b-e76f2d652312; expires=Sun, 03-May-2020 00:14:27 GMT; path=/; secure; HttpOnly\na74qacl051=qaweb403.sfld; path=/; HttpOnly; Secure\n__cfruid=515b3ca5ba0b16ce5ab42e254ddf44ee65cf8261-1588292067; path=/; domain=.http://beeline.com; HttpOnly; Secure; SameSite=None", "Cache-Control"=>"private", "Strict-Transport-Security"=>"max-age=300; includeSubDomains; preload; always;", "Content-Security-Policy"=>"frame-ancestors *.http://beeline.com *.http://iqnavigator.com *.http://iqnavigator.eu *.http://beeline.to *.http://beelinetowork.io http://beeline.to http://beelinetowork.io https://beebot-bot-sales.azurewebsites.net https://beebot-bot-prod.azurewebsites.net https://beebot-bot-proj.azurewebsites.net https://beebot-bot-hfreg.azurewebsites.net https://beebot-bot-reg.azurewebsites.net https://beebot-bot-pct.azurewebsites.net https://beebot-bot-qa.azurewebsites.net https://beebot-bot-hfqa.azurewebsites.net https://cdn.botframework.com https://directline.botframework.com", "X-Xss-Protection"=>"1", "Totalserverpagetime"=>"569", "Cdnheader"=>"{\"AuthenticationDate\":\"2020-05-01T00:14:27.5297229Z\",\"AuthenticationType\":\"Auth0CwsLogin\",\"ImpersonationType\":\"Self\",\"UserName\":\"gmurray\",\"OrganizationType\":\"Beeline\",\"Organization\":null,\"ImpersonateeUserName\":null,\"ImpersonateeOrganizationType\":null,\"ImpersonateeOrganization\":null,\"CFRAY\":\"58c54d6a6ce7e3c2-DTW\"}", "X-Content-Type-Options"=>"nosniff", "X-Ua-Compatible"=>"IE=edge", "Accept-Ranges"=>"bytes", "Cf-Cache-Status"=>"DYNAMIC", "Expect-Ct"=>"max-age=604800, report-uri=\"https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct\"", "Server"=>"cloudflare", "Cf-Ray"=>"58c54d6a6ce7e3c2-ATL", "Cf-Request-Id"=>"026f2eb6830000e3c259184200000001"}, see debug logs for body D, [2020-04-30T20:14:27.620041 #40704] DEBUG -- : body: [{"friendlyId":"4961","assignmentId":"a425c44e-868e-4bb4-b80e-ad64d1060011","status":"Expired","subStatus":"Extension in Progress","approvalStatus":"HM Approval","modifyDate":"0001-01-01T05:00:00Z","clientName":"Foggy"}]```

:slightly_smiling_face:

ALl good, that?s better - but unfortunately I still can?t see why it might be failing :disappointed:

Hi Beth, I am attempting to install the correct version of the app which is 1.80.1. However, I am running on a windows machine. Does the script support windows? If not, is there a manual way around it?

No, it doesn't support Windows, sorry. You don't have cygwin?

You can always push your changes and they'll run on Travis.

It's a very quick build.

Is there any work being done for incorporating pact specification version 3.0 in PactNet ? So that it can be used for contract testing with things like kafka streams ?

Someone was working on message pact for .net

I think they lost momentum on it though.

There's a branch here: https://github.com/pact-foundation/pact-net/tree/message-pact

Thanks for the quick response @bethskurrie !

has joined #pact-net

Hey .net people - anyone have some free lockdown time and interested in helping with this feature? https://pact.canny.io/feature-requests/p/create-e2e-example-that-runs-on-appveyor-or-similar-to-help-diagnose-issues

has joined #pact-net

Hi there, I am a QA engineer. I am just very new to contract testing and read about PACT online today. I am not sure this is the right place to ask. Please redirect me if not. I would like to know whether its right to use PACT in my scenario. I have a rest api to test, which takes data from a third party wcf service , process and gives some result. Can someone please advice ? THanks in advance

You probably won?t be able to test the WCF part, but you likely can test between your consumers and the rest api, if it?s JSON based.

I?m guessing the WCF service is SOAP/XML based.

Hi @bethskurrie, I can probably help out with this :+1: The Ruby sample looks like a good source to crib from.

@a.smith that would be amazing!

We want the barest of bare bones end to end scenarios - it's not about showing best practice, it's about providing people with something they can quickly modify to demonstrate bugs or problems they're having.

The feature mentions AppVeyor. I'm happy to put it there, but just wanted to check what you use for CI in other repos, and whether you think it would be worthwhile keeping it all together?

Appveyor is the one I've used

As long as it's something that people can get a free oss account with their github account when they fork it, I'm not fussy though

Like, when you fork a github repo, you can see the Travis build comes pretty much automatically if you have a Travis account.

It looks like Travis does Windows now though.

They didn't when I set up the appveyor builds years ago. Travis would be my preference, if it's available for oss projects, because all our other builds are on Travis

:+1: Also .NET does not-Windows now :wink:

Let's go with Travis then. I've taken a fork of the Ruby repo and will see what I can do with this over the next few days

has joined #pact-net

Awesome sauce @a.smith

> Also .NET does not-Windows now We seem to have more people with http://Pact.NET problems with Windows on than we do on not-Windows :cry:

Ah well, between my work laptop and my personal laptop, I've Windows, macOS and Ubuntu covered, so... :crossed_fingers:

has joined #pact-net

Hi, any plan soon to support message pact as per v3 spec?

There is an active branch, I suggest jump on the PR for it and help vote/get it thru

I?m about done with this, just trying to wrap my head around the build bits. I?m trying to port the Rakefiles directly to PowerShell?s Invoke-Build, but am somewhat struggling with the provider?s tasks, as I _think_ the magic appears to be mostly within imported gems, and I don?t understand the comment about doing the whole publish-verify flow in Rake. I?ve pushed what I?ve done so far for some feedback: https://github.com/alastairs/pact-net-e2e-example/tree/dotnet-port

Sharing here because I forgot to tick the necessary box :upside_down_face:

Hi @a.smith

I'm just having a look at your net port of the rake tasks.

@a.smith have sent you a PM

PactNet maintainers, I've made a new branch, message-pact-2, which has the latest changes from master, merged into the message-pact branch. I didn't do a straight merge, because I am not a pact-net maintainer or even a .net developer, so I didn't want to screw anything up, but we have a Pactflow customer who is already using the message branch who needs some of the fixes from master. cc @neil

:thumbsup: I?ll get master merged into message-pact

Ta. Who knows what's outstanding on the message work?

TODO.txt

Our customer is already using it quite happily apparently.

cool

It?s not crazy far off, it just lost momentum as the person who was driving it just disappeared (I?m guessing got super busy with other stuff)

We all know what that's like.

The problem with OSS. Lost momentum due to lack of free time.

Yep, it?s constant struggle. I always feel bad for not putting in more time.

I didn't do much the year the bots were born.

Has anyone successfully used Pact-Net with Azure Event Grid?

I have just merged master into the `message-pact` branch. Are you ok with me deleting `message-pact-2` ?

hi, can anyone please redirect me towards a sample implementation of CDC using pact-net? I got the Consumer side. But I am struggling to understand the provider verification part. I feel that the ".net workshop" thing is incomplete and misleading.

I am looking forward to kind of a more complete implementation...

@arindam.datta Can you elaborate on what you're missing?

If I am not missing anything, following are the things which seem either incomplete or erroneous to me: ? the Provider test project doesn't have any relation with the actual Project api project ? Any endpoint except "/provider-states" throws 404

Gotcha. This side of things is a bit confusing :slightly_smiling_face: The Provider tests are almost a framework for running the API project and executing the pacts against it. There?s a lot of boilerplate to running Provider tests in .NET right now. https://github.com/pact-foundation/pact-net#2-tell-the-provider-it-needs-to-honour-the-pact is where you should start; the `using` statement ~50% through the first code sample starts the API project and tells it the URL on which it should listen: in this sample, that URI is `http://localhost:9222`. Note from the second code sample that the `TestStartup` class composes an instance of `Startup` from your API project and the `ProviderStateMiddleware`. This middleware is a test-only piece of boilerplate, and is included to support the `state` item from the Pact specification. If you?ve not added any State lines to your pacts, you don?t need this bit. The `ProviderStateMiddleware` is a door into your API project, that allows you to put it into the appropriate state for that part of the pact. It is called by Pact on the `/provider-states` endpoint, and maps the `state` string from the pact to an arbitrary action. The mapping is in `ProviderStateMiddleware.Invoke()` and the `_providerStates` dictionary, the specific example state and action are defined in the `ProviderStateMiddleware` constructor. To be honest, I found the provider states portion _really_ confusing until I talked it through at length with a colleague. I?d love to see this part of the library simplified for developers. For our use case, testing Azure Functions, we actually spin up the Azure Function application standalone, and run the `provider-states` route in a completely separate http://ASP.NET Core application, which monkeys around with the database (or whatever) on behalf of the Function. This of course assumes that the state is outside of the Function and not in-process somehow? Meaning no disrespect whatsoever to the library maintainers, the Pact-Net README is quite general (=> vague), and a bit out of date (=> confusing). You might find the https://github.com/pact-foundation/pact-net/tree/master/Samples/EventApi/Provider.Api.Web.Tests clearer, especially if you step through it with the debugger.

> To be honest, I found the provider states portion really confusing until I talked it through at length with a colleague. I?d love to see this part of the library simplified for developers. For our use case, testing Azure Functions, we actually spin up the Azure Function application standalone, and run the provider-states route in a completely separate http://ASP.NET Core application, which monkeys around with the database (or whatever) on behalf of the Function. This of course assumes that the state is outside of the Function and not in-process somehow? that?s a decent strategy, but does require knowledge

Agree, provider states are hard to wrap your head around

(also, thanks heaps for that workshop)

@arindam.datta you might want to check out https://github.com/pact-foundation/pact-workshop-js. It?s a solid workshop that explains all of the concepts (in JS). But they should translate across to .NET pretty well

Thanks @matt.fellows. I am already doing that. things are so neat with Node and so clumsy with .Net.

@a.smith, thanks for such a detailed response. It was really helpful. Indeed the other sample test project which you mentioned was somewhat clearer than the workshop samples.

Glad it helped @arindam.datta :slightly_smiling_face:

Hi, my provider verification tests running inside docker container fails even though the interaction is passed. The logs from the container as below: `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/pact_spec_runner.rb:34:in `run'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:69:in `run_with_pact_uri_object'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:50:in `run_specs'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:21:in `call'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:13:in `call'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:169:in `verify_pact'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:43:in `block in call'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:42:in `collect'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:42:in `call'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:34:in `call'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/cli/verify.rb:56:in `verify'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/cli/custom_thor.rb:17:in `start'` `from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/app/pact-provider-verifier.rb:33:in `<main>'` `DEBUG: This pact is still in pending state for ProviderSvc as the successful verification results have not yet been published.` `Test Run Failed.` `Total tests: 1` `Failed: 1` `Total time: 13.6085 Seconds` `The command '/bin/sh -c dotnet test "./tests/ProviderSvc.Tests/ProviderSvc.Tests.csproj"' returned a non-zero code: 1` `##[error]The command '/bin/sh -c dotnet test "./tests/ProviderSvc.Tests/ProviderSvc.Tests.csproj"' returned a non-zero code: 1` `##[error]The process '/usr/bin/docker' failed with exit code 1`

Wheras, the interaction is passed: `Content-Type: "application/json"` `I, [2020-06-08T16:06:17.959905 #146] INFO -- response: Status 200` `D, [2020-06-08T16:06:17.960059 #146] DEBUG -- response: connection: "close"` `date: "Mon, 08 Jun 2020 16:06:17 GMT"` `server: "Kestrel"` `transfer-encoding: "chunked"` `has status code 200` `has a matching body` `includes headers` `"Content-Type" which equals "application/json; charset=utf-8"` `1 interaction, 0 failures`

Can anyone please give me a clue what I am doing wrong?

Can anyone please provide me a clue where I am going wrong about this :point_up:?

@arindam.datta your test failed: ```Test Run Failed. Total tests: 1 Failed: 1``` Do you have any assertions in your test, or just the pact verification?

hi @a.smith, I don't have any assertion. It's just the pact verification `verifier.Verify()` that's it.

However, you can also see, in the log that the interaction is passed (I have only one interaction)

Earlier the log was not complete. Let me give you the complete log.

```2020-06-08T16:06:20.0522439Z Verifying a pact between ConsumerSvc and ProviderSvc [PENDING] 2020-06-08T16:06:20.0523115Z Given Data doesn't exist for user username 2020-06-08T16:06:20.0523416Z A post request with ApiRequest 2020-06-08T16:06:20.0523675Z with POST /api/v1/home 2020-06-08T16:06:20.0523928Z returns a response which 2020-06-08T16:06:20.0524927Z DEBUG: Setting up provider state 'Data doesn't exist for user username' for consumer 'ConsumerSvc' using provider state set up URL http://localhost:9223/provider-states 2020-06-08T16:06:20.0526439Z I, [2020-06-08T16:06:17.783962 #146] INFO -- request: POST http://localhost:9223/provider-states 2020-06-08T16:06:20.0527420Z D, [2020-06-08T16:06:17.784182 #146] DEBUG -- request: User-Agent: "Faraday v0.17.3" 2020-06-08T16:06:20.0528037Z Content-Type: "application/json" 2020-06-08T16:06:20.0528675Z I, [2020-06-08T16:06:17.959905 #146] INFO -- response: Status 200 2020-06-08T16:06:20.0529423Z D, [2020-06-08T16:06:17.960059 #146] DEBUG -- response: connection: "close" 2020-06-08T16:06:20.0529841Z date: "Mon, 08 Jun 2020 16:06:17 GMT" 2020-06-08T16:06:20.0530108Z server: "Kestrel" 2020-06-08T16:06:20.0530564Z transfer-encoding: "chunked" 2020-06-08T16:06:20.0530831Z has status code 200 2020-06-08T16:06:20.0531079Z has a matching body 2020-06-08T16:06:20.0531319Z includes headers 2020-06-08T16:06:20.0531915Z "Content-Type" which equals "application/json; charset=utf-8" 2020-06-08T16:06:20.0532202Z 2020-06-08T16:06:20.0532386Z 1 interaction, 0 failures 2020-06-08T16:06:20.0534537Z /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish.rb:103:in `publish_verification_results': Error returned from verification results publication 400 {"errors"=>{"provider_version"=>["Version number 'default' cannot be parsed to a version number. The expected format (unless this configuration has been overridden) is a semantic version. eg. 1.3.0 or 2.0.4.rc1"]}} (Pact::Provider::VerificationResults::PublicationError) 2020-06-08T16:06:20.0536655Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish.rb:35:in `call' 2020-06-08T16:06:20.0537901Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish.rb:21:in `call' 2020-06-08T16:06:20.0542977Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish_all.rb:22:in `block in call' 2020-06-08T16:06:20.0544297Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish_all.rb:19:in `collect' 2020-06-08T16:06:20.0545823Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish_all.rb:19:in `call' 2020-06-08T16:06:20.0547094Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/verification_results/publish_all.rb:10:in `call' 2020-06-08T16:06:20.0548328Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/rspec/pact_broker_formatter.rb:28:in `close' 2020-06-08T16:06:20.0549557Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:209:in `block in notify' 2020-06-08T16:06:20.0550713Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:208:in `each' 2020-06-08T16:06:20.0552047Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:208:in `notify' 2020-06-08T16:06:20.0553195Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:243:in `close' 2020-06-08T16:06:20.0554349Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:196:in `close_after' 2020-06-08T16:06:20.0555523Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:174:in `finish' 2020-06-08T16:06:20.0556657Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/reporter.rb:76:in `report' 2020-06-08T16:06:20.0557836Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:115:in `run_specs' 2020-06-08T16:06:20.0558960Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:89:in `run' 2020-06-08T16:06:20.0560069Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/rspec-core-3.9.1/lib/rspec/core/runner.rb:71:in `run' 2020-06-08T16:06:20.0561244Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/pact_spec_runner.rb:88:in `run_specs' 2020-06-08T16:06:20.0562415Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/provider/pact_spec_runner.rb:34:in `run' 2020-06-08T16:06:20.0563674Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:69:in `run_with_pact_uri_object' 2020-06-08T16:06:20.0564897Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:50:in `run_specs' 2020-06-08T16:06:20.0566268Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:21:in `call' 2020-06-08T16:06:20.0567531Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-1.49.3/lib/pact/cli/run_pact_verification.rb:13:in `call' 2020-06-08T16:06:20.0568787Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:169:in `verify_pact' 2020-06-08T16:06:20.0570291Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:43:in `block in call' 2020-06-08T16:06:20.0571565Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:42:in `collect' 2020-06-08T16:06:20.0572803Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:42:in `call' 2020-06-08T16:06:20.0574026Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/app.rb:34:in `call' 2020-06-08T16:06:20.0575297Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/cli/verify.rb:56:in `verify' 2020-06-08T16:06:20.0576603Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run' 2020-06-08T16:06:20.0577746Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command' 2020-06-08T16:06:20.0578835Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch' 2020-06-08T16:06:20.0579912Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/thor-0.20.3/lib/thor/base.rb:466:in `start' 2020-06-08T16:06:20.0581110Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.30.1/lib/pact/provider_verifier/cli/custom_thor.rb:17:in `start' 2020-06-08T16:06:20.0582231Z from /app/tests/ProviderSvc.Tests/bin/Debug/netcoreapp3.1/pact-linux-x86_64/lib/app/pact-provider-verifier.rb:33:in `<main>' 2020-06-08T16:06:20.0582920Z DEBUG: This pact is still in pending state for ProviderSvc as the successful verification results have not yet been published. 2020-06-08T16:06:20.0583294Z 2020-06-08T16:06:20.0583412Z 2020-06-08T16:06:20.0583611Z 2020-06-08T16:06:20.0583987Z [91mTest Run Failed. 2020-06-08T16:06:20.0584396Z [0mTotal tests: 1 2020-06-08T16:06:20.0584633Z Failed: 1 2020-06-08T16:06:20.0611265Z Total time: 13.6085 Seconds 2020-06-08T16:06:20.6811884Z The command '/bin/sh -c dotnet test "./tests/ProviderSvc.Tests/ProviderSvc.Tests.csproj"' returned a non-zero code: 1 2020-06-08T16:06:20.6955808Z ##[error]The command '/bin/sh -c dotnet test "./tests/ProviderSvc.Tests/ProviderSvc.Tests.csproj"' returned a non-zero code: 1 2020-06-08T16:06:20.6968648Z ##[error]The process '/usr/bin/docker' failed with exit code 1 2020-06-08T16:06:20.6989096Z ##[section]Finishing: Docker Build```

@a.smith I think I found the issue. It could be this: ```1.49.3/lib/pact/provider/verification_results/publish.rb:103:in `publish_verification_results': Error returned from verification results publication 400 {"errors"=>{"provider_version"=>["Version number 'default' cannot be parsed to a version number. The expected format (unless this configuration has been overridden) is a semantic version. eg. 1.3.0 or ``` Seems like some configuration issue when running on CI build. So, the exception might be occurring while trying to publish with "not supported" version format.

If you?re verifying from a Pact Broker and publishing results, that makes sense

Looks like you should update the version property

has joined #pact-net

Hi there - im keen to start using Pact with some of our serverless, event driven lambdas (AWS sqs event triggers) ... have done a bit of reading on Message Pact, which seems ideal for what we would want to implement, however it seems like this port may not be available for some time in http://Pact.Net. My question is, is there any advice or code samples on handling this scenario in the meantime? One thought i've had is, I could spin up a test web server and wrap our lambda with an api call, but if I can avoid all that extra boilerplate it would be good...

That's actually what happens under the hood.

There was some movement on the message branch - I believe some people are using it successfully already.

ahh interesting

I think it's mostly tests and refactoring that are outstanding. There's a TODO file on that branch that you can have a look at.

yea I took a look at the Todo - is there a way to get access to this? ie are they publishing the branch nuget package?

I'm not sure, sorry. I'm not a .net developer, so I don't know how they're doing it.

I'll ping the person who was doing it and find out how.

cool cool - thank you!!

Thanks @neil :slightly_smiling_face:

This is now the latest message pact branch build https://ci.appveyor.com/project/SEEKJobs/pact-net/builds/33161464

has joined #pact-net

Initially, we cloned the message-pact branch and use the PactNet project directly into our tests. Later on, we wanted to ensure that all test projects used the exact same version of PactNet, so we published it as a nuget package and shared it with all the test projects. We followed the instructions from https://docs.microsoft.com/en-us/nuget/create-packages/creating-a-package#create-the-nuspec-file to build a nukpg based off a nuspec file. Neil's method is probably the simplest, so I would go with that approach first

Thanks for the updates

has joined #pact-net

has joined #pact-net

Hi there, When pulling from the broker and verifying on the provider side. Are the ServiceProvider/HonoursPactWith supposed to filter the contracts verified? pactVerifier .ServiceProvider("ProviderService", ServiceUri) .HonoursPactWith("ConsumerService") .PactBroker(PactBrokerUri, uriOptions: new PactUriOptions(PactBrokerUsername, PactBrokerPassword)) I have added a new ConsumerService2 contract for the ProviderService in the broker and it seems to be pulling/verifying that contract as well? PactNet 2.5.4 PactBroker https://hub.docker.com/layers/pactfoundation/pact-broker/2.57.0.0/images/sha256-b2c82e7533631074fbfc13f162d7ee3b474186f4cf1d26b28bfca2d3b11a1264?context=explore