[FAB-3575] Add unit test instructions to docs

- Add make unit-test info
- Add test coverage info
- Fix link

Change-Id: Ie73a566c867372067353e8f595c09e7c8b634b66
Signed-off-by: David Enyeart <enyeart@us.ibm.com>
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>

Author: denyeart

docs/source/dev-setup/build.rst

@@ -21,6 +21,14 @@ Use the following sequence to run all unit tests
     cd $GOPATH/src/github.com/hyperledger/fabric
     make unit-test
 
+To run a subset of tests, set the TEST_PKGS environment variable.
+Specify a list of packages (separated by space), for example:
+
+::
+
+    export TEST_PKGS="github.com/hyperledger/fabric/core/ledger/..."
+    make unit-test
+
 To run a specific test use the ``-run RE`` flag where RE is a regular
 expression that matches the test case name. To run tests with verbose
 output use the ``-v`` flag. For example, to run the ``TestGetFoo`` test
@@ -31,6 +39,8 @@ call/excecute
 
     go test -v -run=TestGetFoo
 
+
+
 Running Node.js Unit Tests
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 

docs/source/testing.rst

@@ -1,6 +1,30 @@
 Testing
 =======
 
+Unit test
+~~~~~~~~~
+See :doc:`building the fabric <dev-setup/build>` for unit testing instructions.
+
+See `Unit test coverage reports <https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-x86_64/>`__
+
+To see coverage for a package and all sub-packages, execute the test with the ``-cover`` switch:
+
+::
+
+    go test ./... -cover
+
+To see exactly which lines are not covered for a package, generate an html report with source
+code annotated by coverage:
+
+::
+
+    go test -coverprofile=coverage.out
+    go tool cover -html=coverage.out -o coverage.html
+
+
+System test
+~~~~~~~~~~~
+
 [WIP] ...coming soon
 
 This topic is intended to contain recommended test scenarios, as well as