Any words for me please

Sounds like a pretty clear message pact use case, have you read about it before?

Yes I did

Do you have any more specific questions? It's pretty wide open, I'm not sure I know how to help 🙂 Like you said, the consumer says "I expect messages in this shape" and the provider says "I will send messages in that shape for you", and everything else about the broker interactions works the same as synchronous Pact tests, afaik.

I would agree with Boris’s sentiment here

Do you have any more specific questions? It’s pretty wide open, I’m not sure I know how to help

You are agnostic of the transport mechanism in MessagePact, you just care about testing the message.

some random messaging examples I pulled together https://github.com/YOU54F/pact-logical-replication

Please pardon my ignorance

that would be where you business logic is, where you would process the message and do something

aah

code usually needs to be separated out so the business logic of dealing with the messages is agnostic of its transport mechanism, (like hexagonal arch practises) so essentially you can swap out the underlying transport mechanism without affecting your business logic. That way you can test the bit that processes the message, without having to worry about kafka, or grpc, etc.

Ok so if I understand it right. In my case. 1. I need to validate the content of the JSON payload which gets generated as a result of a database write. 2. This write is a result of a POST call to an endpoint So from what I see const wal2JsonHandler = function (wal2JsonEvent: Wal2JsonEvent) { console.log(wal2JsonEvent) // if (!wal2JsonEvent.xid || !wal2JsonEvent.change) { if (!wal2JsonEvent.change) { console.log(wal2JsonEvent); throw new Error("missing change data"); }

It’s okay Sachin! I can understand and emphasise with you, as I was in that position prior to learning about contract testing, and more of an insight into what the developers were doing, and trying to cut overlaps in testing, and push concerns down the stack. Glad things are beginning to fall into place. I’m still learning every day!

Yeah, great that it's making more sense 🎉 and also maybe a separate tip: sometimes it's better to step away from the code, and draw a diagram of the important pieces, then put a circle (or a box, or whatever shape you like) around the bits that are relevant to this testing case.