#C9UN99H24 We are facing issues with multipart file upload contract testing. Getting 'Missing start boundary'. Do we have multipart support at consumer side? We are trying with both pact versions 3.0.0 and 4.0.0, both results same error. If someone has encountered same issue, please provide us the remedy.

Hey hey and happy Friday everybody ralph wave I am pleased to point you in the direction of our launch webinar for Pact Plugins, which is now live on YouTube. 📺 If this has whet your appetite, you can sign up for our Build a Bear Plugin Workshop on the 13/14th December 👉 https://docs.pact.io/events/plugins-framework-workshop

hi! any comments on this ? https://pact-foundation.slack.com/archives/C5F4KFKR8/p1670415366082719

Hey all! Hope to see some of you later in our build a Pact plug-in workshop https://docs.pact.io/events/plugins-framework-workshop Where you will create, publish and utilise your own plug-in in a pact test

Hello! The Europe Plugins Workshop is starting now 👉 https://docs.pact.io/events/plugins-framework-workshop Join @Yousaf Nabi (pactflow.io) and I if you want to get your hands dirty writing your very first plugin 🔌

Hi folks, I don’t know if that can be interesting for some of you. I wrote a little command line to generate interactive diagrams of relations between ms. Here you can find the repo: https://github.com/ManoManoTech/pact-graph-network and some screenshots.

Pact needs you. Yes, you! I promise I won’t take long and you can get back to dreaming about Xmas puds. We don’t sleep here at Pact and are always thinking about our community. We’ve launched an annual survey with the hope to get input from you, big or small. Any contribution is valuable. If you have contributed to any Pact Open Source projects or have engaged with Pact social media and Slack, we'd love to hear your thoughts and experiences! https://forms.office.com/r/ccxYTMxhJm Also if you are itching to do some more advent of code all year round, we’ve got some interesting projects in the pipeline you can sink you teeth into! More to come soon!

hello 🙂 more questions about record/release 🙂 https://docs.pact.io/pact_broker/recording_deployments_and_releases#recording-support-ended-for-a-release

Recording support ended for a release
When a released application is deemed to be no longer supported, call pact-broker record-support-ended. This will stop all pacts for this version being returned for verification by its providers, and remove it from consideration when checking if an integrated application is safe to deploy.

does this mean, that this version also will be considered as not deployed ? use case - we have 3 components • all 3 were deployed ( deployedOrReleased returns all 3 ) • 1 was marked as released ( deployedOrReleased returns all 3(+1 but still 3 ) ) • released component was marked as record-support-ended will deployedOrReleased still return all 3 components ?

Hello all! I’ve done a quick search on docs.pact.io and on here and couldn’t find anything relevant. I know there were conversations in the past around supporting feature flags. What are the current recommendations?

👋 (couldn't find an intro channel so posting hello here) - I'm Paula, lead engineer at Zopa Bank (UK), using Kotlin/Kafka and TS on the FE. Looking into Pact to provide contract testing for our microservices as well as our BFFs and excited to chat more!

Ran a presentation today at work (Tesco Bank) on Pactflow, it went down a treat! We have lots of integration challenges in our environment and I may have just persuaded the higher ups that we can give this a shot.

How would people feel about pact-uk / pact-austrailia / pact-<location> style rooms. I would love to meet more Pact advocates, champions in the UK (especially anyone in Leeds), in person and it might be great to help people find communities local to them.

Sounds fun!

Just read @Yousaf Nabi (pactflow.io)’s wrap up of 2022. What an amazing community. I’m so proud to be a part of it. https://docs.pact.io/blog/2022/11/17/pact-2022-end-of-year-wrapup

Question about best practices for picking up changes to pactfile. Context: 2 microservices, called

PotatoConsumer

and

PotatoProducer

ireland 🥔 with separate everything - pipelines, repos, deployable artifacts. Owned by a full-stack team that communicates well.

PotatoConsumer

updates the Pactfile (for

$reasons

). The update would cause a failure in

PotatoProducer

because it no longer upholds this contract. HOWEVER, because the pipelines etc are all separate, the failure in

PotatoProducer

doesn't get picked up until the next time someone touches it, six weeks after `PotatoConsumer`'s deployment to production (let's assume it fails in a subtle and unnoticed way). What's the best way to avoid this without ending up with pipelines doing super weird things to each other?

Do you have recommendation when a code base is both consumer and provider? Do you create 2 distinguished tasks? How do you identify provider/consumer test to run? One of our team created 2 task:

testContractConsumer

and

testContractProvider

then used tag annotation

# build.gradle.kts
useJUnitPlatform {    
      includeTags("consumer")    
}

And in the test file

@Tag("provider")

or

@Tag("consumer")

Hello! Can I just double check that if a pacticipant supports both HTTP and message protocols, that you’d need to use two different pacticipant names?

Good news! Last week's contract testing talk went down very well at work amongst the engineering practice. In the new year we are going to run a proof of concept. A lot of the services we use are SOAP, what does Pact have to say about contract testing SOAP?

Is there pact support for erlang

👋 , Hello! Question about pact cli

can-i-deploy

Is it possible to specify the version of a Pacticipant through the environment? Basically we would like to do this

pact-broker can-i-deploy --pacticipant AConsumer --version ${gitHash} --pacticipant AProvider --environment prod

This should only check for the Provider version with the environment prod. We are currently using pact-node and I couldn’t find a way to do this

I'm working on a tool that includes PACT support and I'm trying to make it fit as good as possible. I understand testing for an optional attribute does not make sense as another consumer might want it to be there. However, if I describe a scenario (by giving provider states) where the returned array should be empty, can we not verify that? After reading documentation and doing some testing, I come to these conclusions: 1. A scenario where the array contains at least one item is verifiable. 2. A scenario where the array contains max=1 item is verifiable. 3. A scenario where the array contains max=0 is not verifiable (I can specify an empty array, but PACT would still allow a non-empty array). A real world example of scenario 3 would be: Given a provider state of items with only state 'declined' searching for items with state 'accepted' would result in an empty array I could theoretically have 3 interactions: - Interaction 1: tests items in the array - Interaction 2: tests for array length == 1 under specific circumstances - Interaction 3: tests for array length == 0 under specific circumstances It therefore seems arbitrary to allow

max=1

but not

max=0

.

Can anyone shine some light on the above? By the way a big fan of Pact, and I will be able to continue without max=0 but I would like to gain some more understanding, thanks!

HI guys! Reading about Pact and thinking about using it. I have a simple usecase (I think). I want to write a test that sends http to external service, record the request-response in pact json format, then replace the external service in the test with pact-mock-server. I think it must be one of the simplest uses but I can't figure how to register the request-response in pact format. Is there a way to launch pact-proxy-server that would forward my requests and record them against responses?

I can certainly create my own but would not want to reinvent the wheel

Hi All. I've managed to create a consumer pipeline that creates the contract, publishes the contract to the broker, calls a webhook for the provider pipeline to be ran and the can-i-deploy step checking the broker status. However the webhook succeeds when it gets a 201 and moves on to the can-i-deploy job before the provider has chance to run its pipeline and upload a potential new contract to the broker. What would be the best approach here? Is there a way to wait for the provider pipeline to run before the can-i-deploy check is ran? Thanks

Hey guys, I’m running into a basic issue while running provider side tests in the CI I’m using pact-go and using pact-ruby-standalone in my local machine. However, while running the tests in ci, it returns -

exec: "pact-provider-verifier": executable file not found in $PATH

Do I need to run

pactfoundation/pact-cli:latest

as part of my application container before running the pact test?

Hi Pact team We are about to migrate our internal framework which is based on spring (boot 2.7.7, spring 5.x) to spring boot 3. Spring boot 3 comes with Spring 6, java 17 (minimum) and migration of javax ee8 to jakarta ee9. Spring recommands to look at any third party libraries for the usage of javax ee8. We are using Pact junit5spring that comes with spring 5 and javax ee8. Could you please tell me if you plan to upgrade to spring 6 and support jakarta 9 ? Have a nice day

ralph wave How do every one! Hope you had a lovely chilled out break with family, loved ones and friends, and are having a brilliant start to the year. I am back in action from today, after a lovely break away, so will be catching up on various slack threads, GitHub messages, pull requests, issues. Feel free to give me a nudge. Good to be back in the land of pact open link

Hi Team, I am a QE engineer and I would like to introduce Contract testing to our team. In our service which I have taken for writing a POC using Pact, we make thrift RPC calls to other services. How can I write a Pact contract test for Thrift calls? I request you to guide me on this.

Hi, I am a Developer who also would like to introduce contract testing to my team/company. I am not able to successfully install pact via NPM on an Amazon Ec2 instance with CentOS Linux 7. I get many errors related to 'g++' not found (gyp errors), and even after installing a c++ compiler, still have errors related to it. On the other hand, on a physical MAC laptop I have no issues at all installing Pact via NPM. Anyone here ever installed PACT on a bare bones Linux machine and got it working?