I would simply say that testing APIs with pacts is a better approach than e2e testing.. Overall e2e testing is something you want to get rid off, cos development loop with it is too long and not modular.

All you should care about in an API testing is its specification correctness. Whats below should be tested by component tests or even units.

This approach more or less already has a concensus in api world. Im surprised there are still ppl doing e2es.

> Im surprised there are still ppl doing e2es.

You're surprised that there are people actually testing that things work after integration, interacting with the system as a user would?

I'm surprised there are still people who don't.

No, I'm surprised people still use e2e tests as they are not the best way to test what you described..

There are better ways, like the ones I've described. We are not longer in 90s..

ps. e2e tests are not the same as manual testing, so they do not even fully cover your case. They are expensive and take long time to run, while simple pact build step provides pretty much the same value and is pretty much instant while making it easier for all developer teams to track api changes..

You seem to be very focused on the API... but that's only half the product :-)