binman: Run code coverage tests
authorSimon Glass <sjg@chromium.org>
Mon, 27 Nov 2017 03:26:01 +0000 (20:26 -0700)
committerSimon Glass <sjg@chromium.org>
Tue, 16 Jan 2018 01:29:21 +0000 (18:29 -0700)
Binman has 100% test coverage for the code as it is at present. To
encourage it to stay that way, run the code-coverage test as part of the
normal U-Boot tests.

This is RFC because it requires the Python code coverage tools to be
available.

Signed-off-by: Simon Glass <sjg@chromium.org>
test/run

index af1219fdda98a3825796bb3a650024674a7f5820..d5631b802af52a224ad112a5fd501cc5c1aec8b1 100755 (executable)
--- a/test/run
+++ b/test/run
@@ -23,6 +23,13 @@ run_test ./tools/patman/patman --test
 run_test ./tools/buildman/buildman -t
 PYTHONPATH=build-sandbox_spl/scripts/dtc/pylibfdt run_test ./tools/dtoc/dtoc -t
 
+# This needs you to set up Python test coverage tools.
+# To enable Python test coverage on Debian-type distributions (e.g. Ubuntu):
+#   $ sudo apt-get install python-pip python-pytest
+#   $ sudo pip install coverage
+PYTHONPATH=build-sandbox_spl/scripts/dtc/pylibfdt run_test \
+       ./tools/binman/binman -T
+
 if [ $result == 0 ]; then
        echo "Tests passed!"
 else