-
Notifications
You must be signed in to change notification settings - Fork 40
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
93 increase test coverage #101
Conversation
…previous implementation.
…` utility function.
…ng from `User.rate` and it is already validated over there.
…working as expected" and removed the overly used word "properly" from test names and doc strings.
…ssary call to `Task.update_schedule_info()` as it is already handled on the `Task` side.
…tor for the `reviews` attribute instead of `_reviews`. * [#93] Removed the unused `Task._validate_start()` method.
…ndependent_path()` methods.
…_defaults()` method.
Okay so, the test coverage was much lower than what I thought it was (99.96%). Because I was appending the coverage reports while doing my tests, and after updating the code continously for hours, the coverage report data had errorously marking uncovered lines as covered. So, in reality more lines were missing. Anyways, I updated the tests and now the test coverage is really 99.67% . So again, we are practically covering 100% of the code with tests. |
The test coverage is now 99.94% and the 3 lines of code that the tests are not touching are related to Windows where I'm running the tests in macOS. So, practically Stalker is 100% covered with tests.