-
-
Notifications
You must be signed in to change notification settings - Fork 238
Fix test framework running against real devices #1235
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1235 +/- ##
==========================================
- Coverage 92.60% 92.57% -0.04%
==========================================
Files 101 101
Lines 6644 6657 +13
Branches 706 707 +1
==========================================
+ Hits 6153 6163 +10
- Misses 370 372 +2
- Partials 121 122 +1 ☔ View full report in Codecov by Sentry. |
rytilahti
left a comment
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.
Tested on L530 and it did seemingly work (i.e., I saw the state of the bulb changing), but got some errors from a completely unrelated model:
FAILED kasa/tests/test_bulb.py::test_bulb_sysinfo[L510B(EU)_3.0_1.0.5.json-SMART] - voluptuous.error.MultipleInvalid: expected float for dictionary value @ data['longitude']
FAILED kasa/tests/test_bulb.py::test_hsv_on_non_color[L510B(EU)_3.0_1.0.5.json-SMART] - assert not True
FAILED kasa/tests/test_bulb.py::test_non_variable_temp[L510B(EU)_3.0_1.0.5.json-SMART] - Failed: DID NOT RAISE <class 'kasa.exceptions.KasaException'>
|
I can confirm that the tests now no longer crash for the EP40M, however the following errors remain: I believe that the docs failure is due to the test being run from the within Meanwhile it appears that the time test may be failing because the fallback time is the same as the current time, which may be the same as the actual device time. I suggest using the unix epoch instead as the fallback time. Running the tests multiple times in a row shows that it is an intermittent failure, meaning it depends on if you get lucky and how bad your network latency is. |
This should now be fixed
That's correct. You should now be able to run this with
I've now excluded this from physical device testing so it should be skipped. |
|
A couple of errors, but the model is now correct. Copying a couple of lines from the source for context: |
|
I'm a bit late on the follow up, but for the sake of the records, I can confirm that all device tests now pass when run against the EP40M for the final merged commit 71ae06f (including when run the top level directory). |
|
Many thanks @ryenitcher! |
No description provided.