-
Notifications
You must be signed in to change notification settings - Fork 666
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
Switch unit tests from unittest.mock
to SDK & in-memory exporter
#303
Comments
I don't think this is actually done. #306 fixed that for wsgi and Flask, but there are other cases where mock is used: opentelemetry-python/ext/opentelemetry-ext-http-requests/tests/test_requests_integration.py Line 34 in c8b336d
|
Merged
c24t
added a commit
that referenced
this issue
Apr 20, 2020
Update tests to use TestBase as described on #303. Co-authored-by: Yusuke Tsutsumi <yusuke@tsutsumi.io> Co-authored-by: Chris Kleinknecht <libc@google.com>
I think it's solved now by the above PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See #290 (comment).
Currently tests are cumbersome to write and actually we probably don't want to test which API calls are made but what Spans would result in most cases. For this a SDK with in-memory exporter would be better than using
unittest.mock
.The text was updated successfully, but these errors were encountered: