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

@Lewis Cowles has left the channel

Hi all! On the documentation page I found https://docs.pact.io/pact_nirvana the line: "This guide focuses on the scenario where the consumer and provider are both being deployed to an environment rather than released to customers (e.g. a mobile app). That workflow is slightly different, and that guidance will be coming soon." --> Does anyone know if this one is already there??? And where I can find it? 😉 Thanks!

@Evan Rademacher has left the channel

Hi There! I am trying to implement

CI/CD

with pact but there some things that is not clear how to implement it with two different repository!

CI CD scenario:
after contract changing event which it triggers by consumer, we should run provider test pipeline and after failing the the provider pipeline, we need to fail the consumer pipeline as well

I have read the documentation of the CI/CD workshop and followed how

can-i-deploy

could help but I could not completely implement these step on my own Do you have any blog post recommendation to share ?

Hi team, I'm trying to complete a PoC using pact for contract testing. I've managed to create Consumer Driven pact test and push them to a pact-broker running on a docker container locally. Now I would need to create a Provider verifier but I really don't understand the steps there (I'm using Rust, by the way). I would appreciate some guidance if you guys already went through this.

@PK has left the channel

Is it known, that several Deep-Links within the documentation are broken? I'm talking about ones that jump to an anchor tag using a # in the url. Some seem to just have disappeared, some have weird reasons like https://docs.pact.io/implementation_guides/jvm/provider/gradle#publishing-pact-files-to-a-pact-broker which is used at https://docs.pact.io/getting_started/sharing_pacts#language-support . The heading the link refers to still exists, but it seems like it's no longer an anchor. From what I saw so far, it seems like the documentation is scattered across several repos, but maybe this can be detected automatically nevertheless?

Hi There! I have a question regarding the documentation for the CI/CD setup guide, specifically step 7, Diamond level. In the chart in the section "Let's record our deployments," for the provider workflow in the PR validation pipeline part, we first: 1. verify pacts with [mainBranch] and [deployedOrReleased] selectors, which checks if my provider PR is compatible with mainBranch consumers in all environments. Why is it necessary to then use

can-i-deploy --to-environment ...

when the result is already known from the previous step? Could someone help me understand this part? Everything made sense up until now. Thanks!

Excuse me for this newbie question. I am trying to get started. I signed up using pact.io , but when I try to login to my workspace, I get this. I used the same email, etc. How do I get access to my workspace?

I just want to inform you that the second golang link on the page https://docs.pact.io/pact_broker/advanced_topics/consumer_version_selectors is broken.

Hi there, i updated the golang examples on the consumer_version_selectors. • docs.pact.io PR-339 Have a nice day.

Hello. I would like to make a branch and PR the additon of running the pact-broker service in an azure app service. I cloned down the repo and tried to branch and push up my branch, but said I an not authorized. it asked me to fork but failed auth as well. I am not using the same email address as my profile for my github account. who can help me gain access?

Hi! I think there's an error in this example in the documentation. Shouldn't it be:

...

const interaction = provider
      .addInteraction()
...

return interaction.executeTest

...

instead of

provider.executeTest

as

executeTest

is not defined in

PactV4

class but it is in

V4UnconfiguredInteraction

You’re right - thanks! Would you be open to submitting a PR? It’s this file that needs updating (it gets synced to our docs automagically)

New to Pact and perhaps I'm being obtuse, but I'm finding the 5 minute getting started to be hard to follow, particularly the first parts on how to run stuff. The first part states, "Simply hit the green ▶️ button, and the output will be displayed in the terminal below. Give it a shot now". When I click the green ▶️ button, a new browser tab is opened at https://replit.com/@mefellows/Getting-Started-Intro#index.js. That is, no output was displayed in the terminal below. Then under "Ways to run" section, it says, "When you've picked an option, click the corresponding button". The first 2 options are about cloning a copy of the sample repo, but then what? Do I have to build anything? Do I just run

npm run test:consumer

? I didn't try the 3rd option as I didn't want to sign up for another service just yet. The 4th option is to just run in a browser, which opens a new tab with https://replit.com/@pact/pact-5-minute-getting-started-guide?outputonly=1&lite=true#README.md, but, again, then what? It looks like the same readme, but displayed on replit.com. The only apparent action that seems available is the green ▶️ button at the top. Clicking this open another new tab at https://replit.com/@pact/pact-5-minute-getting-started-guide#README.md with no apparent actions available. What am supposed to do here? I feel like I'm missing something. What am I supposed to see when I "run" things?

Hi team, I noticed that there's a link on the How Pact Work page that's pointing to locahost:3000 instead of the correct link on Pact University. I've made a simple PR here

I spent the whole afternoon to set up the provider in .net 8. No success! There is so much confusion and the examples are outdated. I need to build a proof of concept to propose it at work but it looks like it is not the case anymore

@Spencer has left the channel

Has anyone published using docker? https://hub.docker.com/r/pactfoundation/pact-cli is there any tutorial or doc that can help me out pls, thanks!

developer api does not work anymore: https://smartbear.portal.swaggerhub.com/pactflow/default/getting-started.