-
Notifications
You must be signed in to change notification settings - Fork 9
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
Implement some 'integration' tests #8
Comments
By now, we have integration tests (if they can be called that?) for both the CLI (which by extension tests a lot of underlying stuff) and both the API as well as single-file servers (through d645f80), which test the entire stack as well. Together, and with #7, c. 95% coverage is achieved. Some edge cases remain, like these two exceptions: Lines 77 to 82 in 4d5a7ef
These are hard to test without mocking the GitHub API or somehow providing actual gists of actual users that would trigger these code paths. |
The above is now covered by 476bf58. |
Not doing load testing for now. Automatic scaling takes care of that for us now. Plus, a single instance of the app is probably able to handle tons of requests, since it's async-first and templating/rendering is cheap. |
None
where legal (given the schema)The text was updated successfully, but these errors were encountered: