summaryrefslogtreecommitdiff
path: root/TESTING
diff options
context:
space:
mode:
authorDaniel Silverstone <dsilvers@digital-scurf.org>2017-04-08 13:50:18 +0100
committerDaniel Silverstone <dsilvers@digital-scurf.org>2017-04-08 13:50:18 +0100
commit47e6127d9d9d77d0a391f295fa076b5e1cbad273 (patch)
tree8cfa4bf8035ef54f367e9b91ea0881819a8b1425 /TESTING
parentcba5da5382d73b7ca6b46157889b14e5f6e2ee16 (diff)
downloadgitano-47e6127d9d9d77d0a391f295fa076b5e1cbad273.tar.gz
updates TESTING for COVER_GTT=yesdsilvers/gtt-cover-not-default
Diffstat (limited to 'TESTING')
-rw-r--r--TESTING7
1 files changed, 7 insertions, 0 deletions
diff --git a/TESTING b/TESTING
index f9a9b5b..d648c96 100644
--- a/TESTING
+++ b/TESTING
@@ -314,3 +314,10 @@ should be excluded is not, then adjust the `.luacov` file which is the
configuration for the coverage tool. This is also loaded by the internal
in-tree-only module `lib/gitano/coverage.lua` which is generated at build time
from `lib/gitano/coverage.lua.in`.
+
+If you are trying to get coverage for the `gitano-test-tool` binary in the
+`testing` directory then you will need to **also** pass `COVER_GTT=yes` when
+running the test suite. This distinction is present since around two thirds of
+all invocations of coverable code in the test suite uses the test tool to
+perform some related task, meaning that covering it causes a significant
+slowdown in testing, and increases the cost of generating the coverage report.