From 52434ce533b252da7c706b8820ae766ad820fcfb Mon Sep 17 00:00:00 2001 From: Christopher Ferris Date: Wed, 17 May 2017 17:19:12 -0400 Subject: [PATCH] add UT guidance to CONTRIBUTING.rst Change-Id: I86a76ba5060858b564efcc409999b5e91d96b190 Signed-off-by: Christopher Ferris --- docs/source/CONTRIBUTING.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/source/CONTRIBUTING.rst b/docs/source/CONTRIBUTING.rst index 6412e1dd6b0..38e59153015 100644 --- a/docs/source/CONTRIBUTING.rst +++ b/docs/source/CONTRIBUTING.rst @@ -161,7 +161,10 @@ What makes a good change request? definition. Why? Because many open source developers do Test Driven Development. They place a watch on the directory that invokes the tests automagically as the code is changed. This is far more - efficient than having to run a whole build between code changes. + efficient than having to run a whole build between code changes. See + `this definition`__ + of unit testing for a good set of criteria to keep in mind for writing + effective unit tests. - Minimize the lines of code per CR. Why? Maintainers have day jobs, too. If you send a 1,000 or 2,000 LOC change, how long do you think