2e9d8300de
To assert static objects, we either have to add a method into the object under test itself and recompile on a test run with the activated test method (but also recompile after tests, so that method is gone on release builds). Alternatively we can include the whole .c file in our test infrastructure and save the object in the test directory. So there's no necessity to clean it up prior to a release build and it's contained away. This requires, that the test folder isn't excluded in coveralls.
40 lines
735 B
YAML
40 lines
735 B
YAML
addons:
|
|
apt:
|
|
packages:
|
|
- doxygen
|
|
- graphviz
|
|
- libdbus-1-dev
|
|
- libx11-dev
|
|
- libxrandr-dev
|
|
- libxinerama-dev
|
|
- libxss-dev
|
|
- libglib2.0-dev
|
|
- libpango1.0-dev
|
|
- libcairo2-dev
|
|
- libnotify-dev
|
|
- libgtk-3-dev
|
|
- valgrind
|
|
dist: trusty
|
|
sudo: false
|
|
language: c
|
|
|
|
git:
|
|
depth: false
|
|
|
|
before_install:
|
|
- pip install --user cpp-coveralls
|
|
|
|
script:
|
|
- CFLAGS="-Werror" make all dunstify test-valgrind doc-doxygen
|
|
- CFLAGS="-Werror" make clean
|
|
- CFLAGS="-Werror" make test-coverage
|
|
|
|
matrix:
|
|
include:
|
|
- compiler: gcc
|
|
after_success:
|
|
- coveralls
|
|
- compiler: clang
|
|
after_success:
|
|
- coveralls --gcov llvm-cov --gcov-options gcov
|