Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstream changes in Quarkus leads to failure for a message with a payload #191

Open
michalvavrik opened this issue Mar 11, 2024 · 2 comments

Comments

@michalvavrik
Copy link
Contributor

This could be invalid as I do run tests with released Quarkus Pact (tried it also with 1.3.0) and Quarkus 999-SNAPSHOT and without changing anything in my tests, or changing Quarkus Pact version, I now get tests failing (looks like started in last days).

Verifying a pact between TheConsumer and TheProvider
  [Using File src/test/resources/pacts/TheConsumer-TheProvider.json]
  a message with a payload
      Verification Failed - No annotated methods were found for interaction 'a message with a payload'. You need to provide a method annotated with @PactVerifyProvider("a message with a payload") on the classpath that returns the message contents.

Failures:

1) a message with a payload

    1.1) No annotated methods were found for interaction 'a message with a payload'. You need to provide a method annotated with @PactVerifyProvider("a message with a payload") on the classpath that returns the message contents.

Is this something that will be fixed with the next Pact version or a known issue?

Steps to reproduce:

  1. git clone [email protected]:quarkus-qe/quarkus-test-suite.git
  2. cd quarkus-test-suite
  3. mvn clean test -f test-tooling/pact/
@michalvavrik
Copy link
Contributor Author

cc @holly-cummins

@holly-cummins
Copy link
Contributor

Hmm, the ecosystem CI is testing with Quarkus 999-SNAPSHOT and is passing fine, so it looks like there's maybe a coverage gap in the tests in this repo. I'll have a look at the QE suite and see if I can spot the difference.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants