How does eBay utilize Contract Testing for their Microservices?

[@arifmmdv4612]

I just found your channel, and its great, keep on

[@SoftwareDeveloperDiaries]

Thanks buddy!

[@nlsndev]

Really informative, thx !

[@HemantJadhav-vv4rx]

Great sir❤

[@harshavardhanpabboju1030]

Is it completely cypress Or only pact ? Within the pact library do we have axios , describe and it block? Can we use pact library in cypress ?

[@aprilmintacpineda2713]

How is this different from API testing? How does this compare to API testing? Because it seems like we're already doing this in Cypress API testing, all be it there's no "broker" but it's exactly the same concept, you call an API and check that the response follows a particular shape. On the other end, you call an API and mock whatever other API calls it makes.

[@SoftwareDeveloperDiaries]

API Testing is much broader and ensures that services and their dependencies are well-integrated with each other and produce the right result. For example, one service might request data from another one and API testing with Cypress would verify that. Contract testing on the other hand has a smaller scope, I would say on a single team level. If a team wants to avoid setting up the dependencies (services) from other teams and test their stack in isolation then Contract Testing would be preferred. At the end of the day both are necessary, but API Testing (or what you decsribed can also be called a system-test) lives higher on the testing pyramid, while Contract Testing is lower, since it's less constly to write and execute.

[@mscfit]

you say pact is the best cdct framework - did you do an evaluation that you could share. We are currently debating SCC vs PACT