https://test.pactflow.io/pacts/provider/pactflow-example-provider-js-sns/consumer/pactflow-example-consumer-js-sns/latest sample link is asking for credentials. Cant login using my pactflow credentials. Please help.

You can’t login to Pactflow or you can’t publish to Pactflow?

find examples there ☝️

Spot on Matt Consumer - https://docs.pactflow.io/docs/examples/aws/sns/consumer/ Provider - https://docs.pactflow.io/docs/examples/aws/sns/provider/

Thanks for the response. I have got the above link from https://docs.pactflow.io/docs/examples/js/provider/. "The latest version of the Example Pactflow Consumer/Example Pactflow Provider pact is published here." The here opens the page and asks for credentials. So I have asked for the credentials to see the latest examples.

It is using a public tenant on Pactflow, which you can access here using the credentials `dXfltyFMgNOFZAxr8io9wJ37iUpY42M`/`O5AIZWxelWbLvqMd8PkAVycBJh2Psyg1`. The latest version of the Example Pactflow Consumer/Example Pactflow Provider pact is published here.

Details in the readme for the public credentials

We don't support AsyncAPI If that's what you're asking ?

yes I want to test a message based consumer with BDC.

We don't support that yet sorry. It's something we're aiming for in Q1 2023 (current target)

okay.

Please see https://docs.pactflow.io/docs/examples See Kafka for a Java message based demo

thanks

https://github.com/pactflow/example-provider-java-kafka run

make test

or

./gradlew clean test

- these verify pact contracts generated by the consumer application. The provider does not produce a pact file as an output of it's test phase, it generates a verification result, for the pacts its verified as returned by the providers consumer version selectors

okay. I'm a bit confused here. Please correct me. For http services we have Provider OpenAPi documentation which we upload to Pactflow and against which the consumer pact gets validated. I am in an impression that for messaging this will be the same. The only missing part was the openapi documentation of provider message generator. As you have already mentioned that you do not support async openapi so my expectation was the PactVerifyProvider is the place which generate the provider pact.

For http services we have Provider OpenAPi documentation which we upload to Pactflow and against which the consumer pact gets validated.

For Bi-Directional contract testing. Traditional Consumer-Driven contract testing will use a Pact Provider verification build, where it will pull down Pact files from a broker, which have been generated by the consumer codebases

@Yousaf Nabi (pactflow.io) so for messaging its only consumer driven contract testing? In your Java example the Pact gets created its from the consumer test?

Yes correct buddy. We are aiming for AsyncAPI support in Bi-directional contract testing in q1 2023, but currently it only supports OpenAPI specification. Consumer driven supports both HTTP and message pact.

thanks @Yousaf Nabi (pactflow.io)

See docs.pact.io/selectors for what pacts you are verifying and what compatibility checks you need

@Matt (pactflow.io / pact-js / pact-go) I was interested about message based BDC testing. I was looking for AsyncAPI support for provider. But you have mentioned that Q1 2023 is the current target for that. Is there a specific date you have when I can get that? Thanks