You want to be able to run the provider tests against a locally spun up version of the provider that can control its own data

e.g.

npm start

with dependencies mocked

1. Start dev server 2. Run pact tests 3. shutdown dev server 4. [if on CI] publish verification results 5. [if on CI] run can-i-deploy 6. [if on CI and 5 passes] deploy

general workflow for a pact project

any randomized function or something like that?

also, there are hooks (see the docs) that can fire pre/post test you can use to clear out any state in the database (if necessary) to achieve the same thing

If I said you needed to randomise an email address in your unit test email validation procedure because the email address already existed, you would likely tell me that something is wrong with my unit test. That’s essentially the mindset to bring to this problem