CI enhancements - Githubissues

alanxz commented 9 years ago

An issue to track the misc things I want to do with the CI system

[x] make our build work with the container-based builders on travis. (Benefit being build speed).
[x] add a ubsan build
[x] add an asan memsan build
[x] add a tsan build
[x] add a scan-build static-analysis build (and potentially make it so that it automatically uploads to a github sites page where possible).
[ ] run under valgrind
[x] add an OS X build
[ ] add an iOS build
[ ] add coverage instrumentation using coveralls

Things dealing with testing:

[ ] Move to a testing framework that outputs TAP or xml that can be processed by coveralls
[ ] Set some goals to improve the dismal test coverage
[ ] Set up some integration tests that can be run in travis.

ghost commented 8 years ago

Have you got an idea which testing framework to use? Would you consider a C++ testing framework, even though rabbitmq-c is a C library?

alanxz commented 8 years ago

I'm leaning towards cmocka. Its C, has a mocking framework included, has TAP/XML output, and supports the platforms I care about.

The only downside to CMocka is that newer versions aren't widely distributed on Linux systems. My thought on how to get around this is to include it as a git submodule.

At one point I did think about using gtest (which is C++), unfortunately this didn't work well as rabbitmq-c uses identifiers that are keywords in C++ (which should probably be changed anyway, but thats another issue). For the rare platform that doesn't have a C++ compiler, having an all-C solution is a nice feature.

alanxz / rabbitmq-c

CI enhancements #274