Overall, I'm not sure that the time savings is as big as it first appears, but I think it's great for quick projects.
Overall, I'm not sure that the time savings is as big as it first appears, but I think it's great for quick projects.
This current program just a small step in the right direction. :)
EDIT: Currently, I have a test suite at https://github.com/pksunkara/alpaca/tree/testing which tests the generated client libraries of an example API with the respective server.
A bunch of passing tests shouldn't make you feel comfortable able releasing something to production. Proper code review and monitoring of client failures on your servers should make you confident.
My thinking is that, if trusted to output a library that matches the API spec, there is no need to test that API. However, that does require that Alpaca is well-tested enough to be trusted - would you be happy with tests in Alpaca itself, or should it generate tests too?