Code coverage: Also consider functional tests

Lots of our code depends on the C API and thus can only be tested when that is
available. Hence, it makes sense to also run the functional tests under LuaCov.

Signed-off-by: Uli Schlachter <psychon@znc.in>
This commit is contained in:
Uli Schlachter 2016-02-06 17:18:23 +01:00
parent b823dd4ed4
commit 9e05ff63ce
2 changed files with 10 additions and 1 deletions

View File

@ -13,6 +13,10 @@ return {
include = {
escape_pattern(lib_dir) .. ".+",
-- For things already having the correct path
-- (happens with integration tests)
"^lib/",
},
-- configuration for luacov-coveralls reporter

View File

@ -83,7 +83,12 @@ install:
script:
- export CMAKE_ARGS="-DLUA_LIBRARY=${LUALIBRARY} -DLUA_INCLUDE_DIR=${LUAINCLUDE} -D OVERRIDE_VERSION=$AWESOME_VERSION"
- make && sudo env PATH=$PATH make install && awesome --version && make check
- if [ "$DO_COVERAGE" = "true" ]; then make check-coverage; fi
- |
if [ "$DO_COVERAGE" = "true" ]; then
make check-coverage || exit 1;
sed -i "1 i\\require('luacov.runner')('"$PWD"/.luacov')" build/awesomerc.lua || exit 1
BUILD_DIRECTORY="" tests/run.sh || exit 1
fi
after_success:
# Push updated API docs for relevant branches, e.g. non-PRs builds on master.