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>maint
parent
eeff891ac7
commit
54cc5d29a0
|
|
@ -57,7 +57,8 @@ change, the approach taken by the change, and if relevant how this
|
|||
differs substantially from the prior version, are all good things
|
||||
to have.
|
||||
|
||||
Make sure that you have tests for the bug you are fixing.
|
||||
Make sure that you have tests for the bug you are fixing. See
|
||||
t/README for guidance.
|
||||
|
||||
When adding a new feature, make sure that you have new tests to show
|
||||
the feature triggers the new behaviour when it should, and to show the
|
||||
|
|
|
|||
Loading…
Reference in New Issue