Hi, I wanted to open a new thread, as "cppcheck finding" was hijacked with this CICD / testing ;)
I think the best is the enemy of the good : why not start with a few easy tests ? For example just a mix of tiny / big config files to test the parser. I understand the difficult part of the test is to setup complicated infrastructures with many softwares to test edge cases, but that can be done later. Willy, there is no need to setup and maintain a buildfarm (no one has time for this) : as this is an open project, we can use platform like Travis-CI : all tests are described in a yaml file incorporated in the project. It works out of the box for any project hosted at github. We can use a mirror for this. What is great about these is that you can easily plug syntax check softwares ;) Olivier
