From ee67797c7e4a7d3c71809862ddaee25b2ad6cd78 Mon Sep 17 00:00:00 2001 From: Aldo Cortesi Date: Wed, 2 Nov 2016 10:54:08 +1300 Subject: [PATCH] test coverage: complete branch coverage is NOT a goal Branch coverage means lots of duplication in tests to hit all cases, and I'm not sure it's worth it. At any rate, let's aim for statement coverage first. --- setup.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup.cfg b/setup.cfg index df31020c3..305560a62 100644 --- a/setup.cfg +++ b/setup.cfg @@ -10,7 +10,7 @@ testpaths = test addopts = --capture=no --color=yes [coverage:run] -branch = True +branch = False omit = *contrib*, *tnetstring*, *platform*, *main.py [coverage:report]