Hi, we are using the dockerized version of PactCLI (pactfoundation/pact-cli:0.50.0.20) and we are seeing this error verifying a contract when the provider responds with a

set-cookie

header (I have truncated it for readability purposes)

pact-cli_1                         |       Failure/Error: replay_interaction interaction, options[:request_customizer]
pact-cli_1                         | 
pact-cli_1                         |       NoMethodError:
pact-cli_1                         |         undefined method `strip' for nil:NilClass
pact-cli_1                         |       # /usr/lib/ruby/gems/2.7.0/gems/rack-2.2.3/lib/rack/mock.rb:260:in `block in identify_cookie_attributes'
...

Do you have any clue on how to fix this? Thanks in advance!

Random question, but when we do contract testing, then we create the json files explicitly right. The response that we want, do we write that explicitly in json file before running the Pact test?

I made a podcast about contract testing for Microservices. The first installment we talk about the challenges of testing including domain boundaries, breaking down monoliths and much more: https://anchor.fm/pactman-consulting

👋 @Matt (pactflow.io / pact-js / pact-go) should we expect the consumer to be deployable if the provider has not implemented the business logic for an endpoint which has been declared in an OAS document?

here Is anyone available to have a chat about a Consumer Pact being deployable when the implementation for a Provider endpoint hasn't been implemented?

Hello Folk, Is it possible to write a test on the 404 response? Test always fails, but pact file still genearte.

Next question, I try to publish pact file to Pactflow but got 409 responses like this

Client error: `PUT PATH_OF_PACT resulted in a `409 Conflict` response:
This is the first time a pact has been published for "SsoUserService".
The name "SsoUserService" is very similar to the  (truncated...)

Hey guys I had a question , pact is used to test the integration between 2 services or integration between UI and a service but is there any use case where we can use it to test one single API ? keeping the consumer and producer as the same API and testing different endpoints of that API , does it make sense or possible somehow ?

arrayContaining(X1, ..., Xi, ..., Xn)

as I understand it means "match if and only if the returned array contains at least one instance of each `Xi`" , and allows other non-matching elements to appear in the returned array. Is there a variant of this which says, every element of the returned array must match either

X1

... or

Xi

... or

Xn

?

I see the new feature of Pact as a "Bi-Directional Contract Testing". I really need to know what is different between an old and a new feature.

Hi 👋 if my Provider is tagging an environment, why can't I see it when I run

broker list-environments

?

Hi everyone! 👋. Me and my collegue are doing an internship at a large regional IT-organisation and have been asked to work on a proof-of-concept project to see if Pact could be something that they could implement in their organisation for integration testing and deploy testing etc. Their system is a large system built on many jvm based components built with Maven and running with Mule. It uses AMQ message queues and they want us to test the functionality for testing their components both in pipeline and for integration with other components. I find it rather difficult to find good literature on Pact in these type of enviorments and mainly just for one provider - consumer testing with HTTP. D you guys have any tips or links for me to study and checkout for this purpoise? Thanks 😃

Hello, I had a question. Pact standalone can run on alpine or not? I try to run it from pact-php server not start properly. when I try to run manually I got this error

/var/www/vendor/pact-foundation/pact-php/pact/lib/ruby/bin/ruby: line 6: /var/www/vendor/pact-foundation/pact-php/pact/lib/ruby/bin.real/ruby: No such file or directory

Hello All pactflow platypus slack ! I'm pretty new with pact and I'm looking for french speaking users to "build" a french pact community 🙂

Hello, Does the Pact support testing with multiple Providers? Example like below:

Frontend Service ====> Auth Service
Frontend Service ====> User Service
Frontend Service ====> Order Service

All of the example services run together in the same environment. Is it possible to configure this?

Hi Team. I need to add a request signature to my request before testing from provider side. While i was able to add couple of headers using CustomHeaders, how do i get the entire request so i can add signature and send it In java - @TargetRequestFilter is being used.. do we have something for c#?

Hi, i'm running tests using Jest.

beforeAll(() => mockProvider.setup());
afterEach(() => mockProvider.verify());
afterAll(() => mockProvider.finalize());

And I'm seeing this error. The Jest tests are run inside a docker container.

[2022-03-21 16:53:42.071 +0000] INFO (19 on b0e28777c48a): pact-node@10.17.2: Creating Pact Server with options: 
{"timeout":30000,"consumer":"studio-frontend-consumer","cors":false,"dir":"/app/pacts","host":"127.0.0.1","log":"/app/logs/pact.log","logLevel":"INFO","pactfileWriteMode":"overwrite","provider":"pactflow-example-provider-restassured","spec":2,"ssl":false,"pactFileWriteMode":"overwrite"}
[2022-03-21 16:53:42.135 +0000] ERROR (19 on b0e28777c48a): pact-node@10.17.2: Pact Binary Error: /app/node_modules/@pact-foundation/pact-node/standalone/linux-x64-1.88.83/pact/lib/ruby/bin/ruby: line 6: /app/node_modules/@pact-foundation/pact-node/standalone/linux-x64-1.88.83/pact/lib/ruby/bin.real/ruby: No such file or directory

[2022-03-21 16:53:42.135 +0000] WARN (19 on b0e28777c48a): pact-node@10.17.2: Pact exited with code 127.
[2022-03-21 16:53:42.136 +0000] INFO (19 on b0e28777c48a): pact-node@10.17.2: Removing Pact process with PID: 47

My previous error led me to install

bash

in the container. Any help??

Hi everyone, I have maybe a crazy question. I would like to overhaul our current integration testing system. Lets just say it is a publishing type system but interacts with http like System1 -> System 2 -> System 3 (system 1 takes input and publishes to system2), and some other external actor interacts with system 3 and we want to make sure those interactions are correct and the propagation from system 1 got to system 3. Right now its black box where we interact with system 1, wait a while, and then test and make sure system 3 responds with correct results. In my ideal world, we have scenario 1, it interacts with system1, knows what outputs system 1 should have when it interacts, and that is one test. We then take the exact output of that test and use it to test system 2 and so on. Right now when I look at bidirectional testing, it feels like it just makes sure the interfaces conform, but does not fully replace knowing if the output system 1 created is causing the right results in system 2. Is Pact maybe not the right tool for what I am trying to achieve (replace our end 2 end testing with service level tests) but trust that all the interactions that system1 generate cause the correct interactions in system2. Not sure if this is far too much info to get help on as well but looking for any guidance!

Hey everyone, our company is currently trying to integrate Pact into our nx monorepo and we keep running into errors when trying to run the tests. Was curious if anyone has ever integrated Pact into an nx monorepo that uses angular, jest, and cypress. The initial error we're running into is jest and cypress types clashing when running the Pact test. Our monorepo is configured to support both jest/cypress and we have jest tests in other libs that run fine so not sure what about Pact is causing this behavior.

Hello, In one of our projects (React, NodeJS tech stack) we are using BFF (backend for front end, which in our case is Consumer) to speak to domain services (provider). Any tips on how can I write consumer driven tests for BFF queries?

I'm having trouble with the bi-direction coding kata..

Step5 - npm run deploy

No environment found with name 'production'. Available options: <none found>

Not if you're using the traditional approach Sorry, misunderstood the question. You're asking about bi-directional contracts, right?

Hi, someone at my org would like to join this Slack community - how can I invite them?

do we have any blog/tutorial that teaches us on contract testing with PACT MQ?

Hi everyone, just a question is this possible to generate open api based on pact contract? If so, could someone share me a link to find how does it work?

Hello everyone, my team is currently working on PoC to evaluate the usage of the PactFlow in our APIs. We have a lot of questions that the documentation itself its not very clear how to implement. How can we find some support for this tool?

Hey, all. One of the complaints I am hearing from teams looking at Pact is the amount of work it takes to both create and maintain all the interaction specifications that are included in writing the consumer tests, as well as the work to create and maintain the mocks used by the provider verification tests. We had one team who just didn't have the time to fix the contract tests due to failures when the contract changes, and instead just stopped running the contract tests. I'm curious, have others encountered this challenge? How have you addressed this? Thanks!

👋 Hi everyone! I have a question about how pact would work with SDKs, I have a couple of routes that call different services, and I would like to mock somehow these services instead of calling the real server in order to make my provider pass the verification, is there a particular channel where I can use to ask this question or I can put it here so we can discuss it in depth?

Hello everyone 👋 Today, Beth, Ron and I have some exciting news to share with you. Pactflow has been acquired by SmartBear, a leading provider of software development and quality tools. We will join their API Developer Platform, helping to solve the complex challenges of testing microservices and API integrations that companies are facing as they accelerate cloud-native application development and digital initiatives. We care so much for OSS and are so pleased that SmartBear has a strong and demonstrated commitment to OSS—as proven through the support and scale of Cucumber and Swagger. Through our partnership, we will be able to take contract testing to new heights and help deliver key milestones in Pact’s OSS roadmap. We wanted to take the opportunity to thank you for your dedication and support. Pactflow is not just a SaaS product built by our immediate team but a community of individuals who’ve brought us to this point today. We’ve shared many milestones together and we look forward to sharing many more. Read more on our blog.

Hi guys... trying to join this: Webinar: Using Cypress and Postman for Contract Testing