Pact Foundation

Or maybe this should just be a consumer w/ http client like in your video demo, instead of using cy.request() to send request

Hey Charles! I'll take a look at this next week :+1:(reminder set)

Thanks - I think my usage might be a bit of edge case - but I for sure appreciate the help!

Is there more documentation out there beyond <https://github.com/pactflow/pact-cypress-adapter> for using contracts with cypress?

It’s designed for use with our BDCT feature. See <https://docs.pactflow.io/docs/bi-directional-contract-testing> and <https://docs.pactflow.io/docs/workshops/bi-directional-contract-testing>.

It’s _not_ designed for use with standard Pact verification.

Do you have any specific questions on it?

Matt wrote a blog post about it a while back

<https://pactflow.io/blog/cypress-pact-front-end-testing-with-confidence/>

and we have an e2e demo that you can see in action and run

<https://docs.pactflow.io/docs/examples/bi-directional/consumer/cypress/>

This is an alternative to our initial proposal, which when designed, bi-directional contract testing wasn't a thing, in Pactflow. This technique was used by Contentful, as described <https://www.youtube.com/watch?v=cs5ebVzG_Q4&amp;ab_channel=Contentful|here>

<https://docs.pactflow.io/docs/examples/cypress/>

HTH

Is there a functional difference between using the cy.intercept &amp; cy.usePactWait() vs cy.usePactRequest?

`cy.usePactWait` listens to aliased `cy.intercept` commands <https://github.com/pactflow/pact-cypress-adapter#cyusepactwaitalias--alias>

`cy.usePactRequest` will use Pact to issue the request and `cy.usePactGet` to serialise into a pact file

The former will be used when you app actually issues the request, the second is issuing the request itself, which may not be the same as your app issues (not sure why one would use this use case)

Using Pact &amp; Cypress?

Been itching for provider states and matchers?

You might want to get involved in a review of the following PR's

• <https://github.com/pactflow/pact-cypress-adapter/pull/19>
• <https://github.com/pactflow/pact-cypress-adapter/pull/22>
:rockon:

Hi Team, I am a QE and have just started learning about Pact and looking for the possibilities to get benefit out of it.
Do we have to write Pact tests close to the dev code only? Can we write contract tests in a different repo (other than dev repo) using Pact/Cypress? Would it still serve the purpose?

For others, I’ve answered that here: <https://pact-foundation.slack.com/archives/C5F4KFKR8/p1673381550927689>

:ralph-wave:

I've archived this repo

<https://github.com/pact-foundation/cypress-pact>

as it was just a placeholder with no info, and provided links to the current adapter implementation.

Hey folks,
I created <https://github.com/pactflow/example-bi-directional-consumer-cypress/pull/74> to upgrade React and Cypress as I wasn't able to get the example to work without the updates.  I've used Graphite to break the big change into pieces - <https://app.graphite.dev/github/pr/gotreasa/example-bi-directional-consumer-cypress/23> so that each change can be seen and more easily reviewed.

Thanks for doing that. I’ll take a look at it later in the week - I appreciate the reference to stacking too, that’s a new concept but seems very useful.

<@U9UUY3CU9> <@UELMFD9PG> do you have any comments or anything on the pull request?

Sorry Gearoid, I admit I was not able to get to it yet. It might be a next week thing I’m afraid.

Hey <@U06L86JUV1S>,

I just want to sit down and give it a run through on my local machine, I’m on a shorter week this week, so this has slipped onto next weeks radar.

I’m pretty confident it will get merged without any major changes. I just want to wrap my head around some of the changes, as they will be useful to roll out across other repos.

(we use the base react app example across multiple javascript based Pact & PactFlow examples)

We are super appreciative of the change, as it is a significant load off my plate, so want to take the time and give your changes the proper review they deserve.

Hope that is okay? Feel free to drop me a nudge next week as a polite reminder if you wish

I tried the changes in the example-bi-directional-consumer-msw and saw that they are working there as well.

If you run into any issues running it locally for the cypress repository let me know.  (this change will address all of the open security vulnerabilities as well)

ahh my hero!

is this just a personal itch you are scratching or is this part of a rollout of contract testing in your org?

I've been trying to learn about bi-directional pact testing so that I know how to teach others about it.  So I was having a look at postman, cypress and msw

<@UELMFD9PG> thanks for taking the time to review and merge my change.  Would you like help with updating some of the other examples?  I played around with MSW and have a working code change locally that I could submit as a PR.

Hey dude, that would be amazing :yellow_heart: 

Absolutely no rush on contributions however!

Is there a recommended way to set matchers when using cypress?

That’s not intended to generate matching rules, it’s designed for use with PactFlow bi-directional contract testing feature which doesn’t need them. We _don’t_ recommend using it with a Pact only setting - <https://pactflow.io/blog/a-disastrous-tale-of-ui-testing-with-pact/|that’s a recipe for disaster>