summaryrefslogtreecommitdiffstats
path: root/tags/p/package-contains-python-coverage-file.tag
diff options
context:
space:
mode:
Diffstat (limited to 'tags/p/package-contains-python-coverage-file.tag')
-rw-r--r--tags/p/package-contains-python-coverage-file.tag11
1 files changed, 11 insertions, 0 deletions
diff --git a/tags/p/package-contains-python-coverage-file.tag b/tags/p/package-contains-python-coverage-file.tag
new file mode 100644
index 0000000..0bafff0
--- /dev/null
+++ b/tags/p/package-contains-python-coverage-file.tag
@@ -0,0 +1,11 @@
+Tag: package-contains-python-coverage-file
+Severity: warning
+Check: files/names
+Explanation: The package contains a file that looks like output from the Python
+ coverage.py tool. These are generated by python{,3}-coverage during a test
+ run, noting which parts of the code have been executed. They can then be
+ subsequently analyzed to identify code that could have been executed but was
+ not.
+ .
+ As they are unlikely to be of utility to end-users, these files should not
+ be shipped in the final binary package.