-
-
Notifications
You must be signed in to change notification settings - Fork 28.8k
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
Homematic IP Cloud tests are slow #31794
Comments
OK, I will check how many seconds can be saved. |
Another approach is to drop the fixture completely and instead patch and spec the interfaces in the library. We discussed this before. |
I know, but i have no good starting point for this. The hmip devices are quite complex compared to lights. |
I think a good first step would just be to not load climate devices when testing sensors etc. We're setting up a full homematic system up on each test and then check if 1 out of many entities is the right state. |
The problem
The Homematic IP Cloud tests load a lot of data. 6000 lines. This fixture is used for every test. Right now it takes 43 seconds on my machine to run 83 Homematic IP Cloud tests. Our total test run time is 28 min!
As a quick test I took the existing fixture and removed all clients, devices and groups. Still 34 tests passed.
The fixture for homematic IP cloud should be broken up in a per-device part. So the binary sensor fixture should only contain the info needed for the binary sensor test.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
The text was updated successfully, but these errors were encountered: