Question: API Test Coverage (gin.io + busted + luacov) about gin HOT 3 CLOSED

Interesting question.

I think that the best testing approach for testing GIN applications is integration testing. This is to ensure that everything, from the nginx.conf file to the routes, is properly set, and this is what the usage of the helper hit() allows you to achieve.

The other option, as you state, is to directly hit the routes stack without even starting nginx (just as Rails does for instance in controller tests).

The latter option would allow you to easily set up coverage; the first one does not. However, for the reasons here above I'd keep the integration approach. Therefore, I'd rule out having hit() to call the appropriate handler.

How to set up spies in a clean way for coverage, though, is another question.

from gin.

Yes, I would stick with the integration part, too -- no question. Just trying to find a good way to turn the integration tests into integration + unit tests (with coverage) automatically.
The other option I will need (in the very near future) would be a single nginx instance for a complete test group / suite, because starting/stopping nginx for each single test takes quite a lot of time if you have lots of tests (which I have).

from gin.

Outdated.

from gin.