#535 Test Host Process Crashes After 5.0.1 Upgrade Issue created by adamrodger Version information: • OS: Linux x64 • PactNet Version: 5.0.1 • .Net Version: 9.0 Describe the bug After the upgrade from PactNet 5.0.0 to 5.0.1, I get an error when running provider tests inside a .Net Docker container:

The active test run was aborted. Reason: Test host process crashed

Test Run Aborted.
       _VSTestConsole:
         MSB4181: The "VSTestTask" task returned false but did not log an error.
     1>Done Building Project "/app/tests/MyProject.Pacts/MyProject.Pacts.csproj" (VSTest target(s)) -- FAILED.

Build FAILED.
    0 Warning(s)
    0 Error(s)

Time Elapsed 00:00:03.52
Process exited with code 1
Test ignored: MyProject.ProviderTests.VerifyPacts, ignore reason: Interrupted by build execution timeout

Consumer tests work absolutely fine, it's only provider tests that crash. Steps To Reproduce Unsure currently - it was working fine before the upgrade Additional context The diff between 5.0.0 and 5.0.1 only really has an FFI upgrade in it, so I'm assuming the issue is there and that it's crashing the provider tests. pact-foundation/pact-net

@Erich Zimmerman has left the channel

Hi! We are working on the implementation of PACT in some API projects. We have the following case: One of the endpoints returns an array, and the problem we encountered during provider validation was that the order defined in the contract was different from the one returned by the API. For now, we have resolved it by sorting the array in the contract to match what the provider returns. However, our question is if there is any other way to do this and what best practices we can apply in this case. Thanks!

#538 Messaging pacts - guidelines to provide real message to verifier Issue created by scrocquesel-ml150 I'm working on implementing the messaging verifier. In my case, the provider sends messages to an Azure Service Bus in response to certain interactions. I want to verify that these messages conform to the consumer pact. Looking at the examples, it seems that messages are manually constructed in the tests. #459 call them canned message. IMHO, this introduces a risk of divergence between the actual messages sent by the application and the ones defined in the test. What I’ve done instead is configure the provider to send messages to a Service Bus Testcontainer during integration tests. A MessageProcessor dequeues the messages and transforms them into Pact scenarios. Once all integration tests have passed, I use the collected scenarios with the message pact verifier. What do you think of this approach? pact-foundation/pact-net

#539 Request/Response and messaging in same service; how do we filter? Issue created by robbiewareham I am using PactNet 5.0.1 and I have a service that provides the following: • POST request is made to my service which results in a message being written to a 3rd party queue. I now have two pact files hosted in PactBroker; one generated by the consumer of the POST endpoint, the other generated by the process that reads the messages from the queue. I've implemented the verification by having 2 classes, each with one Xunit test. One class uses

MessagingProvider

and is configured to download from a pact broker:

using var verifier = new PactVerifier(config);
   
 verifier.MessagingProvider("personal-details-api", CreateJsonSettings())
         .WithProviderMessages(scenarios =>
         {
             scenarios.Add("An event is created", _event);
         })
         .WithPactBrokerSource(_pactBrokerUri)
         .Verify();
 }

I was hoping/assuming that this would only download the messaging pact from pact broker but it is also downloading the request/response pact too so fails as it only expects messages. The "provider" name in Pact Broker is the same (which makes sense to me as the provider is the same), but do I have to have unique provider names? pact-foundation/pact-net

#540 How to authenticate to the Provider target endpoint ? Issue created by rpbs Version information: • PactNet Version: 5.0.1 • .Net Version: 8 Describe the bug Not a bug but I'm not being able to pass Authorization with a Bearer to the header of the Pact Uri Steps To Reproduce I have a pact verifier, I need to be able to authenticate to the Provider Uri.

httpVerifier.WithHttpEndpoint(providerUri)

Then I'm calling

Verify()

method Log Output I'm getting 401 Could you guys help me to understand what I'm missing ? pact-foundation/pact-net

#541 feat(verifier): Added support of set_no_pacts_is_error feature Pull request opened by levanoz Added support for the set_no_pacts_is_error feature, implemented similarly to how it's done in pact-js and other Pact libraries. pact-foundation/pact-net

Hi, We have a provider test of an AMQP interaction in Pact. The interaction has a "description" and "providerStates". We added in the test:

.WithMessages(scenarios =>  {
                    scenarios.Add(
                        "scenario description",
                        builder => SetupDescriptionA(builder));
                }, _serializerOptions) ...

and the state handler "prepare data" in the middleware. I would expect the state handler to execute FIRST to prepare the data for the content of the message, and THEN the description handler to execute SECOND so that it uses a messageProducer function to generate the message based on the prepared data, But it is the opposite! This forces us to abandon providerStates and only use descriptions for both setting the environment and producing the message. In case, I misunderstand something please let me know. Thank you in advance!

#542 Sequence of "description" and "providerStates" in messaging provider verification. Issue created by dranidis Version information: • OS: Arch Linux • PactNet Version: 5.0.1 • .Net Version: 8.0.100 • Pact Broker Version (if applicable): NA Describe the bug Description handler is executed before the state handler. Steps To Reproduce The current behaviour can be reproduced with the code in this repo:

<https://github.com/dranidis/pact-dotnet-message-provider>

Expected behavior We have a provider test of an AMQP interaction in Pact. The interaction has a "description" and "providerStates". We added in the test:

.WithMessages(scenarios =>  {
                    scenarios.Add(
                        "scenario description",
                        builder => SetupDescriptionA(builder));
                }, _serializerOptions) ...

and the state handler "prepare data" in the middleware. I would expect the state handler to execute FIRST to prepare the data for the content of the message, and THEN the description handler to execute SECOND so that it uses a messageProducer function to generate the message based on the prepared data, But it is the opposite! This forces us to abandon providerStates and only use descriptions for both setting the environment and producing the message. In case, I misunderstand something please let me know. pact-foundation/pact-net

#543 RFC: Configure a custom port for the mock server Issue created by scrocquesel-ml150 Is your feature request related to a problem? Please describe. I'm running Pact on the host and the client is in a testcontainer. Having a container call the host is a bit difficult and testcontainer has some helpers but it requires to know the server port in advance. Describe the solution you'd like I want to configure the pact listening port in the Options instead of relying on the FindUnusedPort. Breaking Changes No, if the port is not configured, it use the FindUnusedPort. Potential Downsides/Caveats The user is responsible to pass port that is not currently used. Describe alternatives you've considered Start pact first but not very convenient in how the test fixture are writtent Additional context The Js version has such a config https://github.com/pact-foundation/pact-js/blob/8c8348b5188b8819f90b10d26834c222e4e7b744/src/v4/http/types.ts#L34-L37 pact-foundation/pact-net

#514 Improve target frameworks and their package references: Pull request opened by SymbioticKilla Hi @adamrodger, sorry for PR before creating an issue to discuss. I think it is easier to discuss it within PR, if you are interested in this change. 1.) Add net8.0 as a target framework to support latest LTS version and to use latest compile improvements with less package references 2.) Add conditions for package references => net8.0 doesn't need them 3.) Remove net462 => netstandard2.0 is already a compatibility mode framework to support all .NET versions. There is no need to specify old .NET frameworks. 4.) All projects except nuget projects can reference only net8.0. There is no need for multiple target frameworks pact-foundation/pact-net

#523 chore(deps): bump System.Text.Json from 8.0.2 to 8.0.5 in /src/PactNet.Abstractions Pull request opened by dependabot[bot] Bumps System.Text.Json from 8.0.2 to 8.0.5. [Dependabot compatibility score](https://camo.githubusercontent.com/83a80808250b8d7de5b1c5c1881019cdb26e6e54015140cf9970290c2096bdff/68747470733a2f2f646570656e6461626f742d6261646765732e6769746875626170702e636f6d2f6261646765732f636f6d7061746962696c6974795f73636f72653f646570656e64656e63792d6e616d653d53797374656d2e546578742e4a736f6e267061636b6167652d6d616e616765723d6e756765742670726576696f75732d76657273696f6e3d382e302e32266e65772d76657273696f6e3d382e302e35) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting

@dependabot rebase

. --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: •

@dependabot rebase

will rebase this PR •

@dependabot recreate

will recreate this PR, overwriting any edits that have been made to it •

@dependabot merge

will merge this PR after your CI passes on it •

@dependabot squash and merge

will squash and merge this PR after your CI passes on it •

@dependabot cancel merge

will cancel a previously requested merge and block automerging •

@dependabot reopen

will reopen this PR if it is closed •

@dependabot close

will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually •

@dependabot show <dependency name> ignore conditions

will show all of the ignore conditions of the specified dependency •

@dependabot ignore this major version

will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this minor version

will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) •

@dependabot ignore this dependency

will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page. pact-foundation/pact-net

Hey everyone, is there a way to specify the URL to use for pact messages? It seems to grab the base URL from the "WithHttpEndpoint" method and slaps on a port + "/pact-messages". The issue is that the URL we pass in when running this in a pipeline is an APIM URL, so it gets a 404. We need it to use localhost when calling for the pact messages

@Zachary Lysobey has left the channel

#544 MessageProvider listening on localhost returns 404 Issue created by scrocquesel-ml150 Version information: • OS: WSL with Windows x64 • PactNet Version: 5.0.1 • .Net Version: 8.0 Describe the bug I'm trying to verify message interaction for a producer. The sample project in this repo works fine, but with my project, when pact tries to request

<http://localhost:41952/pact-messages/>

, it receive a 404 response without going through the

HandleRequest

method of

MessageProvider

. If I modify the prefix uri with

127.0.0.1

, then it works in all cases. What is important is that the Uri added to the HttpListener must be

127.0.0.1

. Then, the returned uri can be the

ip

or

localhost

it works in both cases. I know it is connecting to the listener somehow because if I comment out the start of the HttpListener, then it cannot connect. There is definetely something going in the middle with

localhost

but I can't figure it out. Steps To Reproduce I didn't succeed yet identifying what's going on. Expected behavior The listener should be able to receive pact_verifier request Log Output

2025-06-20T13:58:12.662599Z DEBUG ThreadId(01) verify_interaction{interaction="A valid message"}: reqwest::connect: starting new connection: <http://127.0.0.1:49152/>    
2025-06-20T13:58:12.662613Z DEBUG ThreadId(01) verify_interaction{interaction="A valid message"}: hyper_util::client::legacy::connect::http: connecting to 127.0.0.1:49152
2025-06-20T13:58:12.662888Z DEBUG ThreadId(01) verify_interaction{interaction="A valid message"}: hyper_util::client::legacy::connect::http: connected to 127.0.0.1:49152
2025-06-20T13:58:12.691760Z DEBUG ThreadId(01) verify_interaction{interaction="A valid message"}: hyper_util::client::legacy::pool: pooling idle connection for ("http", 127.0.0.1:49152)
2025-06-20T13:58:12.691815Z DEBUG ThreadId(01) verify_interaction{interaction="A valid message"}: pact_verifier::provider_client: Received native response: Response { url: "<http://127.0.0.1:49152/pact-messages>", status: 404, headers: {"content-type": "text/html", "server": "Microsoft-NetCore/2.0", "date": "Fri, 20 Jun 2025 13:58:12 GMT", "content-length": "30"} }
2025-06-20T13:58:12.691945Z  INFO ThreadId(01) verify_interaction{interaction="A valid message"}: pact_verifier::provider_client: Received response: HTTP Response ( status: 404, headers: Some({"content-type": ["text/html"], "server": ["Microsoft-NetCore/2.0"], "date": ["Fri, 20 Jun 2025 13:58:12 GMT"], "content-length": ["30"]}), body: Present(30 bytes, text/html) )
2025-06-20T13:58:12.691967Z DEBUG ThreadId(01) verify_interaction{interaction="A valid message"}: pact_verifier::provider_client: body:
<h1>Not Found (Not Found)</h1>

pact-foundation/pact-net

hello people! First time doing contract testing, and would appreciate some help. Im creating a consumer test with: pactBuilder .ExpectsToReceive("response") .Given("Received x") On the producer side I can do: verifier .WithMessages(scenarios => { scenarios.Add("response", builder => { builder. WithContent(() => ""); }); But how do I consume the ".Given("Received x")"? I've tried reading the docs but I could not find anything related to this (Im using Messages not HttpRequests)

Hi, We wanted to write consumer tests for a swagger with oneof, anyOf key words. It seems that Pactflow supports these keywords using

discriminator

, but the Pact.NET library doesn't seems to support this. Could you please let us know, how we should proceed further to test this? Thank you. https://docs.pactflow.io/docs/bi-directional-contract-testing/contracts/oas/keyword-support#general-advice

Hello, Are there plans to upgrade Xunit to xunit.v3?

Hello 👋 I love the idea of Pact, I think it would be perfect for my workplace and have spent some time writing a basic test over a dotnet web API. When setting these tests up I surprised that the tests required my app to be running! Additionally setting up data so that the endpoint even functioned was a pain, as I was trying to test a feature which required data set up ahead of time using other api endpoints. I've got a setup which runs a fake http server, using my actual controller but mocking db calls, which is kind of nice, but I don't like how much additional code and maintenance overhead this will cost us. Question 1: Does Pact require my app to be up and running or can it run some other way? How do you all make it work? Example code of my provider test

using var pactVerifier = new PactVerifier("MyService", config);

pactVerifier
  .WithHttpEndpoint(new Uri("<http://localhost:5001>"))
  .WithFileSource(new FileInfo(pactPath))
  .Verify();

Thanks!

#545 PublishResult with / in the provider branch name fails Issue created by scrocquesel Version information: • OS: Linux • PactNet Version: 5.0.1 • .Net Version: 8 • Pact Broker Version (if applicable): 2.107.1 Describe the bug Trying to publish test results with provider branch "/refs/head/test", result in an error

2025-07-10T21:23:11.928119Z ERROR ThreadId(01) pact_verifier::pact_broker: Failed to push branch refs/head/test for provider version test
2025-07-10T21:23:11.928223Z ERROR ThreadId(01) pact_verifier: Publishing of verification results failed with an error: Link/Resource was not found - Request to pact broker path '/pacticipants/myprovider/branches/refs%2Fhead%2Ftest/versions/test' failed: 404 Not Found. URL: '<https://pactbroker.com/>'

Steps To Reproduce

options.PublishResults(brokerConfig.ProviderVersion, publishOptions =>
                    {
                        publishOptions
                            .BuildUri("<http://test>")
                            .ProviderBranch("/refs/head/test");
                    });

Expected behavior The provider verification result should be published to a branch with a slash. This is a supported value with the pact cli to publish consumer contract. Log Output See above Additional context Replacing

/

with

-

make it works. pact-foundation/pact-net

Hi 👋 we're following this page of the pact-net documentation and running into trouble verifying a Message interaction. The method

PactVerifier.WithMessages

doesn't exist. Using pact-net 5.0.1 Is this a known issue? What can we do to verify a pact containing interactions with type Asynchronous/Message (pact specification v4)

Quick question: I'm trying to set the provider branch when publishing Pact verification results like this:

this.verifier!
    .WithHttpEndpoint(PactServiceUri)
    .WithPactBrokerSource(new Uri(Environment.GetEnvironmentVariable("PACT_BROKER_BASE_URL")!), options =>
    {
        options
        .TokenAuthentication(Environment.GetEnvironmentVariable("PACT_BROKER_TOKEN"))
        .PublishResults(Environment.GetEnvironmentVariable("ADDRESS_PROVIDER_VERSION") ?? "1.0.0")
        .ProviderBranch("main");
    })
    .WithProviderStateUrl(new Uri($"{PactServiceUri}provider-states"))
    .Verify();

However, it doesn't seem to work, the

ProviderBranch()

call seems to be ignored. I'm using Pact .Net 5.0.0.

@Dominick Campbell has left the channel

#546 feat: pactbuilder can be properly disposed Pull request opened by scrocquesel When creating

PactHandle

with

pactffi_new_pact

, it need to be freed with

pactffi_free_pact_handle

. I implement Disposable interface but not sure how to handle unmanaged resource with finalizer. BTW, I see that pactffi has a dedicated method for message interactions (

pactffi_new_message_pact

,

pactffi_free_message_pact_handle

) and use them. It doesn't change the way the consumer test generate its pact file. pact-foundation/pact-net

Hi is this tool still alive for .net ? I was trying to create consumer tests for bi-directional approach , using V4 spec and V3 but non of those examples from docs working. IT seems like documenataion is outdated or tool is no longer supported.

#547 Fix content creation syntax in messaging pacts Pull request opened by indranilmaitihyland pact-foundation/pact-net

#548 Extract PactNet.Interop package with Grpc Sample Pull request opened by max-lancaster I have read through issue #492 thoroughly and examined the source code and feel that I have a decent understanding of what's involved in adding plugin support, specifically for Grpc. I was able to take @Yousaf Nabi (pactflow.io)'s example and create this PR to get some sample Grpc tests working. I have extracted a

PactNet.Interop

package as @adamrodger suggested in Issue #492 . This was not a breaking change since all the classes in this namespace were internal,

PactNet

now references this new package and none of the pre-existing interface methods have changed. Extracting this package made it possible to create bare-bones Grpc plugin tests and is effectively a very "raw" way of using any plugin. Perhaps a next step would be to wrap the bare-bones methods in a more fluent "raw" interface in a plugin package similar to implementations in other languages as @Matt (pactflow.io / pact-js / pact-go) suggested. In any case, as a next step from here I was hoping to start working on an implementation of a

PactNet.Extensions.Grpc

package that follows the conventions established in the existing http and message interactions. An alternative approach here would be to just add

<InternalsVisibleTo Include="PactNet.Extensions.Grpc" />

to the PactNet.csproj file but this allows integration of other plugins in repos outside this one so it depends on whether you want to explicitly allow that or not. pact-foundation/pact-net

Hi all, I’m trying to work with message pacts in PactNet where the consumer expects the payload to be

text/plain

instead of JSON. What I’ve noticed: • On the consumer side, the DSL only exposes helpers like

WithJsonContent(...)

which always serialize the messages to JSON. I don’t see a way to say "the body is raw text and the contentType is `text/plain`". • On the provider side, when using

.WithMessages(...).WithContent(...)

, any

string

gets serialized as JSON and the content type ends up

application/json

. I don’t see an overload that doesn't take the JsonSerializationOptions. So essentially: I don’t see a way in PactNet to produce or verify a message pact where the body is plain text and the content type is

text/plain

. 👉 My questions: • Is this a known limitation in PactNet? • Or is there some sample code / workaround that shows how to handle non-JSON content types (like

text/plain

) in message pacts on .NET? We’re using PactNet 5.0.1 (

PactNet

+

PactNet.Abstractions

). Thanks in advance!

#549 PactNet.sln line endings are in illegal git state Issue created by max-lancaster When interactively rebasing and editing a commit or checking out a new branch the PactNet.sln file line endings get modified which makes a lot of git functionality unusable. Issue is described in this stack overflow issue. I have reproduced this on both Mac Os and Windows so it is not an OS specific defect. To reproduce if you just clone the repo and do a

git status

you will see that PactNet.sln all line-endings have immediately changed. Potential solution is described in the accepted answer of the above referenced SO post. Appears that the root cause may be that line endings were not renormalized (

git add --renormalize .

) when the .gitattributes file was added. pact-foundation/pact-net

@Paul has left the channel