summaryrefslogtreecommitdiff
path: root/DEVELOP
diff options
context:
space:
mode:
authorLee Clemens <java@leeclemens.net>2015-07-07 20:03:34 -0400
committerLee Clemens <java@leeclemens.net>2015-07-09 10:12:40 -0400
commitb1022a4fe462eddf364d4503f285ececaeeb82b4 (patch)
tree922fbe824dd077f7e1ec68d1cf6614b0ebdc930c /DEVELOP
parent4aff396b05136629fa0a8f99705749d84b2cfed7 (diff)
downloadfail2ban-b1022a4fe462eddf364d4503f285ececaeeb82b4.tar.gz
DOC: Use coverage report and optionally coverage html
Diffstat (limited to 'DEVELOP')
-rw-r--r--DEVELOP5
1 files changed, 4 insertions, 1 deletions
diff --git a/DEVELOP b/DEVELOP
index b71f5274..bb7de5c8 100644
--- a/DEVELOP
+++ b/DEVELOP
@@ -56,9 +56,12 @@ following (note: on Debian-based systems, the script is called
`python-coverage`)::
coverage run bin/fail2ban-testcases
+ coverage report
+
+Optionally:
coverage html
-Then look at htmlcov/index.html and see how much coverage your test cases
+And then browse htmlcov/index.html and see how much coverage your test cases
exert over the code base. Full coverage is a good thing however it may not be
complete. Try to ensure tests cover as many independent paths through the
code.