Karate DSL is extremely effective in those situations where you have a microservice still in development, but the "consumer" web-UI dev team needs to make progress. Just create a mock definition (feature) file, and since it is plain-text - it can easily be shared across teams via Git. Since Karate has a binary stand-alone executable, even teams that are not familiar with Java can use it to stand-up mock services. And the best part is that the mock serves as a "contract" - which the server-side team can use to practice test-driven development.
Interesting that you saw sharing via Git as a benefit. If I might tell my story:
At my previous company, we had great success with Postman and sharing APIs. It gave a strong contract-driven development loops, without having to touch the code bases.
When it came time to switch to the real APIs, the front-end team just had to change a base URL.
That works for some, but not for those who would like to keep all their artifacts WITHIN the firewall.
