Hello Pact-Gophers! Would anyone happen to be located in or near London, who has some Pact GoLang experience, and would to speak at a local meetup in September? If so let me know in a thread, and can discuss details!

@Eytan Hanig has left the channel

Hello, I'm trying to run the test from the exemples but I get this error: someone know how to fix it?

Does pact-go support rewriting grpc request headers/body to support provider side testing for handling different states ?

No, but it does support provider states

Is this for auth?

Seeing an issue with protobuf where the consumer test cannot find an enum definition when the message definitions are in multiple proto files. Opened an issue against pact-go with the details - but might be a plugin issue? https://github.com/pact-foundation/pact-go/issues/334

Hi everyone, I have the following test

package events

import (
	"<http://github.com/pact-foundation/pact-go/dsl|github.com/pact-foundation/pact-go/dsl>"
	"systems-management/database"
	"testing"
)

var cenas = func(m dsl.Message) error {
	return processTrackerUpdateEvent(*m.Content.(*TrackerUpdateEvent))
}

func TestMessageConsumer_Success(t *testing.T) {
	pact := dsl.Pact{
		Consumer: "MyConsumer",
		Provider: "MyProvider",
	}

	message := pact.AddMessage()
	message.Given("couves").
		ExpectsToReceive("assadas").
		WithContent(
			//TrackerUpdateEvent{
			//	Tracker:              database.Tracker{},
			//	TrackerUpdateRequest: database.TrackerUpdateRequest{},
			//},
			map[string]interface{}{
				"Tracker":              database.Tracker{},
				"TrackerUpdateRequest": database.TrackerUpdateRequest{},
			},
		).
		AsType(TrackerUpdateEvent{})

	pact.VerifyMessageConsumer(t, message, cenas)
}

and I am getting the error

panic: interface conversion: interface {} is map[string]interface {}, not *events.TrackerUpdateEvent [recovered]
        panic: interface conversion: interface {} is map[string]interface {}, not *events.TrackerUpdateEvent

any help ? thank you 🙏

@Matt (pactflow.io / pact-js / pact-go) is there a good gRPC example of using provider states for setting different states on provider side ?

@Tigran Davtyan has left the channel

Hi all, quick query, if consumer is storing data in to DB without any handler service, how to generate the contract without calling handler's validation code? can we skip that to generate the json without using any code logic to check but go according to some json schema

Our CI server doesn’t have the PACT CLI installed and the teams using the pact-go are seeing an error when running the contract tests in the CI server. Is there a way for teams to have the cli in their repo and mention it in the Go package manager, so that the Go Pact SDK can use that cli for the contract tests ? I see a similar capability exists on the node and pact node version (9) allows us to test using it

@Georg Duemlein has left the channel

Cross posting this here in case anyone knows? https://pact-foundation.slack.com/archives/C02BXLDJ7JR/p1695926833910029

Hi guys, we're extending our tests so I tried to use

pending pact

feature for synchronization. The good thing is it doesn't fail the suite, but it seems the tests are run twice - is that expected? It also seems that the

verifyRequest.AfterEach

is ignored somehow as the second run reports that resources already exist. Maybe I have something bad in my configuration, could you help me find a culprit please? Adding screens and log to the thread.

@Corey Maynard has left the channel

Hey folks, I am trying to run pact-go with

go test -mod=readonly -v .

Getting this error when I include the

"<http://github.com/pact-foundation/pact-go/v2/consumer|github.com/pact-foundation/pact-go/v2/consumer>"

package Is anyone familiar with this?

# <http://github.com/pact-foundation/pact-go/v2/internal/native|github.com/pact-foundation/pact-go/v2/internal/native>
Undefined symbols for architecture x86_64:
  "_pactffi_create_mock_server_for_transport", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_create_mock_server_for_transport in _x003.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_create_mock_server_for_transport)
  "_pactffi_verifier_add_custom_header", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_verifier_add_custom_header in _x005.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_verifier_add_custom_header)
  "_pactffi_verifier_add_provider_transport", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_verifier_add_provider_transport in _x005.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_verifier_add_provider_transport)
  "_pactffi_verifier_new_for_application", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_verifier_new_for_application in _x005.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_verifier_new_for_application)
  "_pactffi_verifier_set_filter_info", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_verifier_set_filter_info in _x005.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_verifier_set_filter_info)
  "_pactffi_verifier_set_no_pacts_is_error", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_verifier_set_no_pacts_is_error in _x005.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_verifier_set_no_pacts_is_error)
  "_pactffi_verifier_set_publish_options", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_verifier_set_publish_options in _x005.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_verifier_set_publish_options)
  "_pactffi_with_header_v2", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_with_header_v2 in _x004.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_with_header_v2)
  "_pactffi_with_query_parameter_v2", referenced from:
      __cgo_df62a8d4863b_Cfunc_pactffi_with_query_parameter_v2 in _x004.o
     (maybe you meant: __cgo_df62a8d4863b_Cfunc_pactffi_with_query_parameter_v2)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
FAIL    //[build failed]
FAIL

Have you run the install step?

Hello, I'm a little confused with the Pact behaviour regarding non-defined states on provider side. Currently, the request is called even when state is not defined. Is it possible to fail the test if the state is not defined on provider? I would love to have tests like these

pending

more then passing. Thx! Log from my test:

023/10/19 13:00:03 [INFO] executing state handler middleware
2023/10/19 13:00:03 [WARN] no state handler found for state: ComponentDetectionQuery progressing
2023-10-19T11:00:03.919419Z  INFO ThreadId(13) pact_verifier: Running provider verification for 'request to return CDQ'
2023-10-19T11:00:03.919461Z  INFO ThreadId(13) pact_verifier::provider_client: Sending request to provider at <http://localhost:43615/>
2023-10-19T11:00:03.919465Z  INFO ThreadId(13) pact_verifier::provider_client: Sending request HTTP Request ( ... )
2023-10-19T11:00:03.921893Z  INFO ThreadId(13) pact_matching: comparing to expected response: HTTP Response ( status: 200, headers: Some({"Content-Type": ["application/json"]}), body: Present(430 bytes) )
2023-10-19T11:00:03.922307Z  INFO ThreadId(13) pact_verifier: Running teardown provider state change handler 'ComponentDetectionQuery progressing' for 'request to return CDQ'
2023/10/19 13:00:03 [INFO] executing state handler middleware
2023/10/19 13:00:03 [WARN] no state handler found for state: ComponentDetectionQuery progressing

...

  request to return CDQ (0s loading, 5ms verification)
     Given ComponentDetectionQuery progressing
    returns a response which
      has status code 200 (OK)
      includes headers
        "Content-Type" with value "application/json" (OK)
      has a matching body (OK)

An important part of contract testing is being able to run your service with mocked out dependencies. We have realized that there’s a great opportunity in contract testing to make “fresh mocks”. Essentially mocks that closely align with their production counterparts, using contract testing to enforce this alignment. We’d like to have mocks that take in requests and look up the appropriate responses by consulting pact interaction files. Logically, we’d need a way of parsing pact interaction files to help us here. We also realize that this desired behavior is very similar to the pact mock server, but we saw that the pact mock server cannot handle multiple interactions. So our questions are: 1. Do you have any suggestions on how to integrate pact with mocks such that we can reliably call our mocks and get similar behavior to production counterparts? 2. Is it possible to expose the Pact interaction file parser (or get a code pointer to it) a. If not, do you know how often the pact parsing logic changes? (We may consider writing our own fork in Golang to avoid CGO issues) 3. Is it a large change to allow the pact mock server to handle multiple interactions at a time? We looked at the code a bit and am concerned about breaking the plugin api. The team would love to jump on a call to brainstorm with you if someone is willing. Let us know! 🙏 cc @Matt (pactflow.io / pact-js / pact-go)

Hello, I've tried to use BeforeEach method and I see problems with multiple state setup. The problem is that BeforeEach runs before every state within one interaction, which basically doesn't make sense as it reset the setup from the previous state. My code:

interaction('Getting application', ({ provider, execute }) => {
    beforeEach(() => {
      provider
        .given("Application exists", appParams)
        .given("Application has components", compParams)
        .uponReceiving('Get app with its components.')
        .withRequest(contract.request)
        .willRespondWith(contract.response);
    });
    ...
   }

The log is like this:

2023-10-24T08:30:08.922544Z  INFO ThreadId(13) pact_verifier: Running setup provider state change handler 'Application exists' for 'Get app with its components.'
beforeeach - clean up
2023/10/24 10:30:08 [INFO] executing state handler middleware
application created
2023-10-24T08:30:09.190301Z  INFO ThreadId(13) pact_verifier: Running setup provider state change handler 'Application has components' for 'Get app with its components.'
beforeeach - clean up
application removed
2023/10/24 10:30:09 [INFO] executing state handler middleware
"create component error": "unable to get the Application"

In the doc I found that multiple state setup is upported in V3 scheme, which is what we're using. Am I doing anything wrong?

hi all, on Concourse pipeline, I am getting this error

=== RUN   Test_HandlerContract
2023/10/24 16:10:39 [INFO] checking pact-provider-verifier within range >= 1.36.1, < 2.0.0
2023/10/24 16:10:39 [ERROR] CLI tools are out of date, please upgrade before continuing

while running

go test

even though I installed the pact-cli, updated the path and got pact-go deps

any one faced similar issue?

Hey guys, I want to clarify some points that I found reading the explanation from the consumer message test: • I didn't find the NewMessagePactV3 function inside the repository... Has it upgraded or changed this method? • I also didn't find the type AsynchronousMessage... We are using inside de userHandlerWrapper that we assume as our adapter, abstracting the implementation and focusing on validating the content of the message. • How can I publish the contract from this test to a Pact Broker?

@Ruth has left the channel

hey all, please correct my understanding I have added contract tests for message pacts using pact-go and got the setup done as below 1. Team A’s Message Pact Consumer side test runs using their JSON model for the data and publishes in Jenkins to the host with git version set to consumer version 2. Team B’s Message Pact Provider side test runs in Jenkins using their JSON Model and verifies against the contract from the host. 3. If there is a model change and both teams not in-sync, contract verification will fail and pipeline will fail, so both teams will have to liaise and fix. The pipeline failures have MSTeams alerts. I was thinking the above is enough to identify the dependency issues and solving the purpose. I haven’t incorporated below things, please advise whether these are required. 1. Publishing only when there is a change? 2. Can-i-deploy check? 3. Webhooks to trigger provider pipeline. Thanks.

Hey all, quick confirmation please for messages-pacts, Consumer test, I have set WithContent like this

"items": dsl.EachLike(map[string]interface{}{

"id":    "1270284",

"qty": dsl.Integer(),

}, 1),

and on Provider test, used the data for verification like

"data": {

"date": "2023-11-06",

"reference": "123",

"items": [

{

},

{

}

]

}

still test is passing. Shouldn't it fail the match? for items

@Cody Jenkins has left the channel

@Lukasz has left the channel

Hello, I'm trying to verify my provider but I have the error: 1) Failed to load pact - Could not load pacts from the pact broker 'https://mybroker.pactflow.io' err := verifier.VerifyProvider(t, provider.VerifyRequest{ ProviderBaseURL: "http://0.0.0.0:8080", Provider: "V3Provider", ProviderVersion: "1.0.0", BrokerURL: "https://mybroker.pactflow.io", BrokerUsername: "myemail@gmail.com", BrokerPassword: "mypassword", BrokerToken: "myToken", Tags: []string{"master", "prod"}, PublishVerificationResults: true, // PactFiles: []string{ // filepath.ToSlash("/workspaces/go/consumer/pacts/PactGoProductAPIConsumer-PactGoProductAPI.json"), // }, If I try locally with PactFiles it's working I can verify my provider but if I change to try with the Broker everytime I have this error Failed to load pact and I don't understand why, if someone can help me it will be nice.