How to do testing of an Exegesis API about exegesis

[jwalton]

This is how I've been doing my tests. I'm using "supertest-fetch" here, which is a library I wrote with a fetch-like interface (mainly I wrote it because the Typescript bindings for supertest are broken. :P)

Supertest (or supertest-fetch) will spin up a server for us on a random port, so I create a server with my exegesis controllers, then I just run tests against the server.

You could instantiate your controllers with some sort of IoC framework, and then it would be easy to stub out all the back-end logic and just test your controllers. You could also test your controllers in isolation without involving Exegesis at all, although one upside to using Exegesis is you get request and response validation more-or-less for free, which is nice.

[Ryan-Gordon]

I have seen testing resources in this repo https://github.com/exegesis-js/exegesis-express/tree/master/test

Would the preferred way to test be :

• CreateServer, having a server created in the testing file
• Mock up 1 or 2 routes with an OpenAPI spec
• Then describe tests