Should https://github.com/pact-foundation/pact_broker/wiki/Terminology#pre-verification be moved somewhere into our docs (and if so, where do we think is most appropriate)? The question has come up a few times recently

On the video on this page, https://pactflow.io/bi-directional-contract-testing/, it seems impossible to click on the other thumbnails (on the strip on the bottom, when pausing, or at the end of the video). Also, it seems impossible to click on the share button. Clicking anywhere just pauses the video. I’ve tried in a few browsers.

In this video, , there is a pointer to docs.pactflow.io/docs/examples, that indicates there should be a section for bi-directional contract testing. I can’t find these examples anywhere on the site. Anyone @here find them?

Hello - question about consumer contacts and drift. It's quite easy for a consumer to define a contract, but how can we easily keep the contract up-to-date and not drift away from the actual consumption of the api. For example, a frontend may define a contract with an backend API, but use only a limited amount from either the request or even more likely the response. The initial contract definition is minimal as we dont want to overstate how we consume the API, however, as the frontend changes and consumes more fields from the backend's api response, how can we be deliberate enough to always make sure the contract is up-to-date. Are there any well defined patterns for this that someone can point out? In my case the frontend is React, but happy to review any pattern for this. Thanks in advance

I do love the power of open source. We use Facebooks docusaurus to generate our site documentation and it seems useful to have code tabs showing the relevant snippets for each applicable language, given Pact is multi language. This feature request we made back in Mar has just got merged and will make our code snippets dreamier https://github.com/facebook/docusaurus/issues/7008#issue-1181303022 As we should be able to link to a specific doc page, and then drill down to the relevant code section for the language you need. So we could re-use the same url for say consumer version selectors in each repo passing a language param, and it takes you to exactly what you need, code wise, with all the generic preamble that surrounds the feature but isn’t worth duplicating in each repos respective readmes

Hi folks, I looking for article, blog... That explains the difference between a schema (like graphQL, grpc, avro ...) and a contract. Because each time I propose to setup Pact, teams answer me, it's not necessary we used graphQL. But for me, it's not the same. It's complementary. I'm searching arguments to convince them.

Discussing the

buildUrl

/

--build-url

option I search on pact-ruby-standalone repo to no avail. I was expecting the standalone project to have this information too. Am I misunderstanding that

pact-ruby-standalone

include feature from pact_broker-client?

I have generated a consumer contract using Pact and uploaded to PactFlow, could someone point me in the direction of how to verify this consumer contract using a Python lambda function ? I see examples for Express and similar in Python but how do I undertake a producer test for a AWS Lambda function ? I am a bit baffled and cannot see any clear examples ?

pact open link pact open link pact open link pact open link The docs sync from the pact library markdown files to docs.pact.io is fixed again. Apologies for the interruption to this service 😆 GitHub decided my account was compromised for some reason and disabled my account and all the tokens at the end of last year. The tokens are now re-generated and updated. pact open link pact open link pact open link pact open link

Hello , thanks for all you help with my questions , can anyone give me a working link to the guide to using Pact and SwaggerHub spec to create a consumer contract , the page in the Docs in https://docs.pactflow.io/docs/bi-directional-contract-testing/tools/swaggerhub/ , the link in section 4.2 Test our Consumer is broken . Thanks

You just create a consumer test in the regular way with Pact or an adapter https://docs.pactflow.io/docs/bi-directional-contract-testing/consumer/ Thanks for the heads up on broken link, this is where it is pointing to

Thanks for raising the link issue, I’ve just fixed it

Hey team, from reading the pact broker cli, we are using

--build-url

when calling

pact-broker publish

but it doesn’t really show anything on Pactflow UI so wonder what it is actually for? It would be great if it shows on UI too. Atm, I am just adding it as a tag. Thanks 👍

hey all! Based on this doc Consumer-Driven Contract Testing CI/CD Workshop there is two main repository: • example-consumer • example-provider I must do the same If I want to apply for my application ? I mean, do I need to create a repo for consumer e other for provider? thanks!

I believe the information here is a bit incorrect.

The current version of the specification is 3.0 for the JVM implementation, and 2.0 for all others.

pact-js

also supports V3 now.

Hi here, What's the best way to handle a provider which has no consumers yet, but you still want to implement the pact flow into the ci? It will return saying

Could not load pacts

(which can be turned into a warning) or it will say

No pacts or verifications have been published for version ... of ...

Hi, I am sorry to ask here, but it seems I didn’t find the answer to my question in the documentation. Which is an ideomatic response from

provide_state

endpoint on provider? How is this response to be used next? In many of the examples and real world project I’ve seen, it returns simply JSON

{ "result": state }

. And I was wondering what benefit I could get from configuring this response?

@Gazal Gafoor has left the channel

Hey all ralph wave Verbose logging, you don't know you need it, until you need it! And you really don't want to go digging around the docs for it. It is one of the most valuable things for maintainers/community members when trying to assist users with issues. Know how to do it, in the Pact library you use? Why not help us document it in a single place, for other users, or let us know how best to present a feature/option in all client libraries, to you (as ultimately we would like to expand this idea out to all pact features) https://github.com/pact-foundation/docs.pact.io/issues/237 Thanks for any help in advance happy hearts

@Kripa Kurian has left the channel

404 on "publishing your OpenAPI Provider Contract to PactFlow" Hi folks, On the page Provider Testing Guide [1], we have a link for a page with details about publishing the OpenAPI specs, but it is broken [2]. 1 - https://docs.pactflow.io/docs/bi-directional-contract-testing/provider/#step-4-publish-your-provider-contract-and-verification-results 2 - https://docs.pactflow.io/docs/bi-directional-contract-testing/provider/contracts/oas#publishing-the-provider-contract--results-to-pactflow

Hey, does anyone know if there is documentation on consumer and provider naming best practices? I'm not looking for format of the name but more the level in which you describe the consumer and provider. For example, in a monorepo with N services deployed, is it each 'service' that may be a consumer? Is it the abstractions within each of those services (maybe they are shared in a reusable package?) ? Then on the provider side, if you have an API that is a proxy to several 'provider' services, should then provider name be the API or each individual service? Thanks if you can help

@Lotem Dagan has left the channel

@Bas Dijkstra has left the channel

Hello, does anyone know if there is a documentation on pact test connecting to an external mock server such as mockoon or postman?

I doubt it. What are you trying to do?

instead of using an internal mockserver, i need to connect to mockoon mockserver. All my API concepts are in there.

@Test
	@PactTestFor(pactMethod = "singleProduct")
	void testSingleProduct(MockServer mockServer) {
		productServiceClient.setBaseUrl(mockServer.getUrl());
		Product product = productServiceClient.getProductById(10L);
		assertThat(product, is(equals(new Product(10L, "28 Degrees", "CREDIT_CARD", "v1", "CC_001"))));
	}

correct me if i am wrong.... it seems that i need to have a working api service before i can use this pact test

No, pact provides a mock service. You can't use external mocks in pact consumer tests

Check out the examples to see how it works