-
Expectation: When using `pathFromProviderState` in a consumer pact test, I expect that the path param in the created pact is replaced by the supplied provider state. That is, when verifying a consumer…
-
Current 'master' branch contains many tests that should fail, but don't because they are not executed:
```
:pact-jvm-server:test
:pact-specification-test:test
:provider:pact-jvm-provider-scalatest…
-
Our Team Lead proposed exciting things when we tried to cover our API endpoint (.NET language) with a contract test, which required binary content in the request body. But, as Matt Fellows mentioned, …
-
This is still an issue with Pact-JVM too
my consumer tests are written in Pact-JS
it logs the value as the correct type
` pact_matching::json: compare_values: Calling match_values for path $.user…
-
I'm getting this error ("Unexpected end event") with pending pacts on pact-jvm version 4.1.17. #1221 mentioned the same thing but these pacts are for a service in production, so I don't think we had p…
-
More of a question...
I'm using pact provider maven to do the pact provider-side tests (pact:verify)
Would it be possible to get some jacoco coverage results using this way?
-
There seems to be an issue with directory resolution in step11 for the `pactDirectory` in consumer `build.gradle`:
```
pact {
publish {
pactDirectory = 'consumer/build/pacts' // --> This does…
JonoH updated
2 years ago
-
MFEs allow for simple, light-weight development environments with one glaring exception - the need to launch devstack or Tutor to interact with back end services, especially the LMS for authentication…
-
### Software versions
- **OS**: Win 10, Ubuntu 22.04.2
- **Consumer Pact library**: Pact JS v11.0.2
- **Provider Pact library**: irrelevant
- **Node Version**: v18.14.1
### Issue Checklist
…
-
Using the repository:
https://github.com/my-calculator-poc/MyCalculatorPACT
It is necessary to create some Tests to consume My-Sum-API with PACT.