-
Notifications
You must be signed in to change notification settings - Fork 21
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
More complete testing thoughts ... #15
Comments
To be honest - CUL doesn't play a big role in my smarthome anymore. Only 3 temp/humid sensors, a EM for gas and a doorbell sensor are left atm. This is working "rock stable" for years now, so I don't have that much motivation to put much time into the cul module ;) |
I personally still have the CUL stick on my CCU with cuxd :-) Other prios till now than change this "running system" :-) |
Hey Sebastian,
I have checked a bit. "Complete" testing for CUL-Net is kind of easy. Setup Net-Server and communication can be handled from both sides.
For serial it is more interesting:
One option is to use the Mock-Features from Serialport ... but as I tested for this we need access to the serialport instance of the cul instance ... because of strict mode and such it is not accessible directly, it would be needed to add some kind of "getSerialport" method ... for testing only ... not great :-(
But only alternative I found would be some kind of virtual serialports using socat or something like this. But this would be needed to be installed and started anytime tests are executed. Not very comfortable
What do you think about the options ?! ;-)
The text was updated successfully, but these errors were encountered: