diff options
| author | Junio C Hamano <gitster@pobox.com> | 2014-11-24 09:43:29 -0800 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2014-11-24 09:43:29 -0800 |
| commit | 54cc5d29a0590c47c6f32d15c867c0199fdd672a (patch) | |
| tree | f7f2eb1c31ce7bc0a18a3cc87c86ab4b8b71d6b9 | |
| parent | eeff891ac756fd97a05476446f15269b714ce4cc (diff) | |
| download | git-54cc5d29a0590c47c6f32d15c867c0199fdd672a.tar.gz | |
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>
| -rw-r--r-- | Documentation/SubmittingPatches | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index e6d46edbe7..bfcf1d1b1f 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -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 |