Commit c103dc0b authored by Michael Niedermayer's avatar Michael Niedermayer

git-howto: replace confusing and incorrect text about he testsuite by mostly a correct text.

Signed-off-by: 's avatarMichael Niedermayer <michaelni@gmx.at>
parent 4e82bdea
...@@ -371,9 +371,10 @@ Next let the code pass through a full run of our testsuite. ...@@ -371,9 +371,10 @@ Next let the code pass through a full run of our testsuite.
@item if fate fails due to missing samples run @command{make fate-rsync} and retry @item if fate fails due to missing samples run @command{make fate-rsync} and retry
@end itemize @end itemize
While the test suite covers a wide range of possible problems, it is not Make sure all your changes have been checked before pushing them, the
a panacea. Do not hesitate to perform any other tests necessary to convince testsuite only checks against regressions and that only to some extend. It does
yourself that the changes you are about to push actually work as expected. obviously not check newly added features/code to be working unless you have
added a test for that (which is recommanded btw).
Also note that every single commit should pass the test suite, not just Also note that every single commit should pass the test suite, not just
the result of a series of patches. the result of a series of patches.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment