aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichał Górny <mgorny@gentoo.org>2017-05-07 20:58:56 +0200
committerGöktürk Yüksek <gokturk@gentoo.org>2017-08-24 14:58:01 -0400
commit727424254a8bff2c1339569b9e0091809e764c6c (patch)
tree2e6601ff5d5b7df4a64c2a98ab531f865e281529 /ebuild-writing
parentebuild-writing/.../src_test: Do not suggest blanking src_test() (diff)
downloaddevmanual-727424254a8bff2c1339569b9e0091809e764c6c.tar.gz
devmanual-727424254a8bff2c1339569b9e0091809e764c6c.tar.bz2
devmanual-727424254a8bff2c1339569b9e0091809e764c6c.zip
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.
Diffstat (limited to 'ebuild-writing')
-rw-r--r--ebuild-writing/functions/src_test/text.xml6
1 files 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>