Hi everyone, had a pretty simple question, how doe...
# general
w
Hi everyone, had a pretty simple question, how does pact.io determine which tests need to pass in order to generate the pact? I haven’t figure this out for scala-pact.
To add more detail, currently we are setting up our contract tests in the same repository as all of our tests for our microservice. My understanding is that we cannot avoid running all of our tests versus just the contract ones. Am I misunderstanding this?
t
Pact has lifecycle hooks that are called at the end of each pact test. It uses those
m
I don't know scala pact very well,. But I suspect this is more of a question about the test runner than Pact.
Pact shouldn't know or care about other testing
t
You don’t have to run all your unit tests to generate a pact file. You could just run the pact ones
👍 2
w
Yeah, I think I’m running into problems with choosing which unit tests to run to generate a pact file if that makes sense? The documentation on scala-pact just seems to use sbt pactTest but this will run all tests. Is there an argument/parameter I need to set
🤷‍♂️ 1
m
w
I am using the scala-pact library
👍 1