commit: 727424254a8bff2c1339569b9e0091809e764c6c Author: Michał Górny <mgorny <AT> gentoo <DOT> org> AuthorDate: Sun May 7 18:58:56 2017 +0000 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> CommitDate: Thu Aug 24 18:58:01 2017 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=72742425
ebuild-writing/.../src_test: Improve the broken test suite explanation Broken test suite is *not* worse than no tests. It just requires significantly more effort from the developers analazying the results. ebuild-writing/functions/src_test/text.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ebuild-writing/functions/src_test/text.xml b/ebuild-writing/functions/src_test/text.xml index f43fae0..f058006 100644 --- a/ebuild-writing/functions/src_test/text.xml +++ b/ebuild-writing/functions/src_test/text.xml @@ -113,9 +113,9 @@ setting <c>RESTRICT="test"</c> in the ebuild. <note> If upstream provide a test suite which doesn't work, consider talking -to them about getting it fixed. A broken test suite is worse than no -test suite at all, since we are unable to tell whether a test failure -indicates a genuine fault. +to them about getting it fixed. A broken test suite requires developers +to investigate each test failure in order to determine whether it is +genuine or indicates a broken test. </note> </body> </section>
