From 19f06c67e45d217c62e0002772a09f07e851b856 Mon Sep 17 00:00:00 2001
From: armando-migliaccio <armamig@gmail.com>
Date: Thu, 8 Oct 2015 11:43:26 -0700
Subject: [PATCH] Add pointers to access Neutron test coverage details

Being aware of what the coverage looks like should help
writing more comprehensive tests.

Change-Id: Idd31edb2695d6b2b3475bfd3b2e9eafd6c12ba8e
---
 TESTING.rst | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/TESTING.rst b/TESTING.rst
index d29728cf42c..d71fa220e15 100644
--- a/TESTING.rst
+++ b/TESTING.rst
@@ -309,9 +309,20 @@ current unit tests coverage by running::
 
     $ ./run_tests.sh -c
 
+or by running::
+
+    $ tox -ecover
+
 Since the coverage command can only show unit test coverage, a coverage
 document is maintained that shows test coverage per area of code in:
-doc/source/devref/testing_coverage.rst.
+doc/source/devref/testing_coverage.rst. You could also rely on Zuul
+logs, that are generated post-merge (not every project builds coverage
+results). To access them, do the following:
+
+  * Check out the latest `merge commit <https://review.openstack.org/gitweb?p=openstack/neutron.git;a=search;s=Jenkins;st=author>`_
+  * Go to: http://logs.openstack.org/<first-2-digits-of-sha1>/<sha1>/post/neutron-coverage/.
+  * `Spec <https://review.openstack.org/#/c/221494/>`_ is a work in progress to
+    provide a better landing page.
 
 Debugging
 ---------