-
Notifications
You must be signed in to change notification settings - Fork 121
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
test: add full coverage #731
Conversation
bytestring sometimes wrapped in ", sometimes in ' |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feature/job-decorator #731 +/- ##
==========================================================
+ Coverage 99.96% 100.00% +0.03%
==========================================================
Files 129 129
Lines 8336 8335 -1
Branches 1857 1857
==========================================================
+ Hits 8333 8335 +2
+ Misses 2 0 -2
+ Partials 1 0 -1
☔ View full report in Codecov by Sentry. |
@@ -158,6 +162,41 @@ def my_entry(a, b: int, c=0, d: float = 1.0, **extras) -> str: | |||
mock_stdout.write.assert_any_call(s3_not_linked) | |||
|
|||
|
|||
@patch("time.time", return_value=123.0) | |||
@patch("builtins.open") | |||
@patch("tempfile.TemporaryDirectory") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For clarity later on, it may be worthwhile to include why these patches are needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps, though I don't necessarily see this case as more opaque than a lot of our testing. Here we mock time to have a predictable job name, open to avoid actually creating any files, and tempdir to assert the correct temp dir gets created and removed
Issue #, if available:
Description of changes:
add unit tests to cover missed lines of code
Testing done:
unit tests
Merge Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.General
Tests
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.