aboutsummaryrefslogtreecommitdiffstats
path: root/setup.cfg
diff options
context:
space:
mode:
authorAldo Cortesi <aldo@nullcube.com>2016-06-02 14:44:06 +1200
committerAldo Cortesi <aldo@nullcube.com>2016-06-02 14:44:06 +1200
commitffca395e48d3909c9f588767978d128c1a6529d5 (patch)
tree1ab022e294df0843eccc2389bf2f326594e93f73 /setup.cfg
parent07f7905f9182ad0098a5a2e37d40ce9b27298380 (diff)
downloadmitmproxy-ffca395e48d3909c9f588767978d128c1a6529d5.tar.gz
mitmproxy-ffca395e48d3909c9f588767978d128c1a6529d5.tar.bz2
mitmproxy-ffca395e48d3909c9f588767978d128c1a6529d5.zip
Honesty in testing
- Don't skip tests that fail - Don't omit console from coverage I'm working on the pathod races, and can't seem to reproduce the failures locally. Also, let's not kid ourselves about the console coverage - it should be tracked. To improve it, we should measure it. Regressions in coverage of the module should be flagged by CI.
Diffstat (limited to 'setup.cfg')
-rw-r--r--setup.cfg3
1 files changed, 1 insertions, 2 deletions
diff --git a/setup.cfg b/setup.cfg
index e83ca0ab..eeaac0c8 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -11,8 +11,7 @@ addopts = --capture=no
[coverage:run]
branch = True
-include = *mitmproxy*, *netlib*, *pathod*
-omit = *contrib*, *tnetstring*, *platform*, *console*, *main.py
+omit = *contrib*, *tnetstring*, *platform*, *main.py
[coverage:report]
show_missing = True