Part 1: Analysis and Specification of Automated API testing based on Swagger definitions -- 2

We have public API's with Swagger definitions. We want an Automated API test to trigger whenever we release a new version of this API (maybe scheduled as well). The test should read the swagger definition of the API and do testing based on that. Whenever a swagger definition change (request / response) we want a new version of the API test to be created. The Automated API test should still test all versions of the API to make sure we are not breaking old versions with the new release. The Automated tests must be able to handle Authentication scenario with OpenID/Oauth2 using idtoken. We should be able to trigger the test with a API-call. We should be able to get alerts in Slack whenever a test fail. This first project is about checking if there are any solutions for this already and if so what is the cost of those. What are the benefits and what are they lacking in terms of functionality. Based on this we want a Specification of how it can be setup. Either developing it or using one of the existing if it's good enough for what we want. As a followup to this we will post another project that will implement this.