-
Notifications
You must be signed in to change notification settings - Fork 45
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
Update tests to use internal sample .osm file #265
Comments
@jmaspons What are your thoughts on this issue? Mock tests are currently only in these four files:
That suggests this, which would be good to do for current (v0.1.2) release: TODO
|
Mock calls are cool! I would keep them in the places where we actually want to check the functionality, ie. All in all, if the test coverage doesn't degrade, both approaches are fine. What can be interesting to reduce the package size is to reuse the mock calls. I don't see why we need different queries for each osmdata_* function. Perhaps different mock calls for different query types (adiff, diff, tags...) is enough if needed at all (.osm files also works for checking all the code paths). |
Most of the tests could be run with no mocking at all, by just using an internal
.osm
file.The text was updated successfully, but these errors were encountered: