search

ckb-next / ckb-next

RGB Driver for Linux
GNU General Public License v2.0
3.24k stars 268 forks source link

Testing and Validation #619

Open neeldug opened 4 years ago

neeldug commented 4 years ago

What is the program's current behaviour?

Currently there is no automated testing and validation, which was previously mentioned in #12 however this was closed in the end as Travis CI was unable at the time to test on various versions of macOS and XCode, this has since changed and so I was thinking that perhaps we should consider resurrecting this issue.

What would you like it to do instead?

Setup a basic Travis CI workflow for PRs and Pushes that runs it against as many versions as the core maintainers would like. The implementation for using many different versions of macOS and XCode is documented very well here, currently homebrew makes use of this multi os build matrix to test new packages.

Any other notes & comments?

Ravenslofty commented 4 years ago

So, I've been thinking about this.

Travis is not very helpful in this situation; whether the code compiles has no correlation to whether it works and the only way we can check if it works is by testing against real hardware.

neeldug commented 4 years ago

While this is true, it would still allow for basic testing to be done prior to merging any changes, and it allows testing for compilation on various platforms, it would be impossible to setup CI to test with the hardware, but at least this ensures some level of compatibility for the software to run on various versions, whereas currently, attempting to test against various OS's by the contributor isn't standard practice and nor should it be.