Covering ZWaveLib with unit tests

Recently I found out that Sigma Designs partly opened ZWave protocol specification to the public. So I decided to cover ZWaveLib (used in HomeGenie and developed mostly by Gene) with unit tests to be sure that it conforms the standards.

Now I’m writing tests for command classes, from the bottom of the list to top. I’m adding comments to classes and to the tests with references to the documentation and also add new methods, that should be implemented, but were not implemented yet. I also did some refactoring to make code testable and more readable, so right now it’s not 100% compatible with MIG library. At the end of this rework, I will need to tune up MIG library to use the new version of ZWaveLib. But I’m trying to make things backward compatible and mark deprecated methods with ObsoleteAttribute.

I configured automatic building, testing, and test covering with Appveyor and Codecov.
If you are a developer and could contribute to this activity - I encourage you to do so.

Here is the link to my fork of repository
Current progress: codecov


I’m not the developer, but if you have a test release of your version, I can test it, if you want.

I have many problems with HG 525 version. Z-Wave devices has many timeout :frowning:

Actually, I’m not doing anything really new, right now I’m just writing automation tests to check implementation compliance with official documentation. So I don’t think that my code can help you with timeout issues, but if describe them more detailed I’ll try to have a look.

3 posts were split to a new topic: ZWave device inclusion timeout