-
-
Notifications
You must be signed in to change notification settings - Fork 160
100% Coverage 🥳 #168
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
100% Coverage 🥳 #168
Conversation
Codecov ReportBase: 91.91% // Head: 100.00% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #168 +/- ##
===========================================
+ Coverage 91.91% 100.00% +8.08%
===========================================
Files 7 7
Lines 297 290 -7
===========================================
+ Hits 273 290 +17
+ Misses 24 0 -24
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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.
Curious about a few things but that's awesome we're getting there!
…ecesary datetime fixture)
So, I applied the minor tweaks but I am not 100% happy with the timeout test, as you can see a Github action failed for a connection issue (I guess)... |
Yep, I just ran the actions again and it does look flaky, not sure why. I'd say that's probably a good place for a mock? |
I simulated a timeout with monkeypatch raising a TimeoutException, this should do the trick. Codecov doesn't look too happy but from the errors it looks like a token issue |
Thank you once again @mutt0-ds, it's merged! 🎉 |
It's been a pleasure @ramnes, I've learned so much by working at your project! Let me know if I can contribute to other things :) |
Hello! I added some tests for the errors and fixed a couple of minor issues (TESTING_PAGE_NAME became a session fixture, I excluded abstract properties from tests and I used "with" statements to test the enter and exit properties of the Client class).
When testing the errors I used https://httpstat.us/ for simulating HTTP errors, let me know if this solution would be OK as I didn't manage to generate this kind of situation with cassettes only. :)
This closes #8 😎