The major pains when setting up load testing APIs are: Create load from multiple client nodes (distributed) that all follow the plan in sync Connect with internal / non-public APIs

I had a conversation recently involving contract testing between partners. The provider provides the contract during their ci/cd process before the deployment. The consumer will validate it and if something fails, the change is rejected and the deployment never occurs. The concept of consumers signing off and blocking deployments is very interesting as it empowers and handles the control to the consumer.