CurlyMoo

Also, don't forget to include that manual page.

This is my 433gpio unittest: https://github.com/pilight/pilight/blob/rewrite/tests/hardware_433gpio_receive.c Which uses the DSO: https://github.com/pilight/pilight/blob/rewrite/tests/libgpio.c

Here is the compile command: https://github.com/pilight/pilight/blob/rewrite/ci/travis-script.sh ----- Also, i'm fine with a seperate hardware module folder like in the protocols, but currently all hardware modules descriptions are put in the...

I understand it's confusing. You were not the first asking that question, so i will refer to the previous answer. https://forum.pilight.org/showthread.php?tid=3504

> Running this on the PI, nothing happens Don't run the bash script, check the `cmake` command to see how you compile with unit test enabled. Once you got it...

> However writing a unittest for the RaspyRFM could be complex as I would have to emulate the behavior of the Chip with all the used registers. I'm afraid I...

That the test failed. But this specific test wasn't implemented well. The new lua unittest doesn't have this issue. The other tests should succeed as well.

Add your test like this here: https://github.com/Phunkafizer/pilight/blob/rewrite/tests/alltests.c#L82 and here: https://github.com/Phunkafizer/pilight/blob/rewrite/tests/alltests.c#L234

You should configure it first in the config: https://github.com/pilight/pilight/blob/rewrite/tests/hardware_433gpio_receive.c#L179-L185

I've build a proof-of-concept that might work: Place all files in the cmake build folder libgpio.c ```c /* Copyright (C) 2013 - 2016 CurlyMo This Source Code Form is subject...