SubmittingPatches: refer to t/README for tests
There are general guidelines for writing good tests in t/README but neither SubmittingPatches nor CodingGuidelines refers to it, which makes the document easy to be missed. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Nov 24, 2014 at 09:43 UTC
54cc5d29a0590c47c6f32d15c867c0199fdd672a
1 file changed
+2
-1
Documentation/SubmittingPatches
+2
-1
@@ -57,7 +57,8 @@ change, the approach taken by the change, and if relevant how this
57
differs substantially from the prior version, are all good things
58
to have.
59
60
-Make sure that you have tests for the bug you are fixing.
60
+Make sure that you have tests for the bug you are fixing. See
61
+t/README for guidance.
62
63
When adding a new feature, make sure that you have new tests to show
64
the feature triggers the new behaviour when it should, and to show the