-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create unit/integration tests #82
Comments
You are absolutely right @onionhammer. In principle, generation tests don't need to connect to an actual service, as it only requires the metadata response which could be mocked, making verifying the results more accurate. |
Unless we really need a set of complete end to end integration tests, if it will add any value |
I've had some success hosting webapis in-proc (started by the test), not that much harder to do, then we actually exercise the httpclient. |
Interesting. @onionhammer care to share an example of how you used it? |
in a base test, you basically instantiate an HttpServer object (new HttpServer(config)). I can dig up the code, but it's similar to this: http://blogs.msdn.com/b/youssefm/archive/2013/01/28/writing-tests-for-an-asp-net-webapi-service.aspx |
What about testing the JavaScript client? |
I've not done much JS unit testing, there are some good options I'm sure, and it would be valuable, but you'll have to get someone else to answer that question :) |
We need some unit tests!
What we need most (imo) is automatic testing of code generation, ensuring it succeeds and is able to perform web api requests against a test service.
The text was updated successfully, but these errors were encountered: