Investigate the feasibility of unit testing swagger spec generation

[myssto]

As we have started to heavily rely on swagger / swashbuckle for cross-project compatibility in our ecosystem, it is becoming more and more tedious to manually inspect the json content of the swagger spec every time changes are made to the document generator. It would be very useful to have a unit testing framework in place that can validate the content programmatically.

Hopefully through this we can achieve a setup that can completely mock the swagger generation for the API so that we can confidently unit test changes to the generator (for example the custom document filters in API.SwaggerGen). This will greatly improve testing coverage, code quality, efficiency, and most importantly my sanity!

[majorro]

Why would some framework be needed? It can be done in some way like this, just make some dummy controller with test cases or mock contexts with moq

[myssto]

As written I use 'framework' as sort of a catch-all when really I'm just meaning to say any solution that will work. My initial thought is that it will take a lot more effort than the code you linked. There are more things that augment the ApiExplorer and SwaggerGen in our project than I can name off the top of my head, and all of them have some significance on the outputted swagger spec.