-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
Tests for zwave services #6937
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
Tests for zwave services #6937
Conversation
@armills, thanks for your PR! By analyzing the history of the files in this pull request, we identified @balloob, @andrey-git and @turbokongen to be potential reviewers. |
@@ -554,7 +554,7 @@ def start_zwave(_service_or_event): | |||
hass.services.register(DOMAIN, const.SERVICE_TEST_NETWORK, | |||
test_network, | |||
descriptions[const.SERVICE_TEST_NETWORK]) | |||
hass.services.register(DOMAIN, const.SERVICE_STOP_NETWORK, stop_zwave, | |||
hass.services.register(DOMAIN, const.SERVICE_STOP_NETWORK, stop_network, |
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.
line too long (80 > 79 characters)
Remove |
You can see the progress locally too using py.test --cov --cov-report=term-missing |
I wrapped up the rest of the service tests, and I removed zwave init from .coveragerc. Still a lot that needs to be testing, but I figured this gives us a starting point. We can add it back it if we want to wait until more coverage is added. |
It drops us from 94% test coverage to 93% 😢 but okay, let's do it but let's make sure we have it up to at least 93.5% before 0.43 ! |
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.
🐬 ok to merge when merge conflicts resolved.
Description:
For #6437
This should wait until after #6813 since it will need to be rebased.