ctests-costs-benefits: define false positive

A false positive could either be "not a bug" or a bug that is not
worth the time or complexity to fix. For the purpose of evaluating
the tests, the distinction is not important.

diff --git a/development/autotests/ctests-costs-benefits.txt b/development/autotests/ctests-costs-benefits.txt
index e24ef60d21f385c8f642b0b6232bf4b99787e789..772770ebb09a88c38640b82c169e5c8c86827a2d 100644 (file)
--- a/development/autotests/ctests-costs-benefits.txt
+++ b/development/autotests/ctests-costs-benefits.txt
@@ -15,7 +15,8 @@ Below we can try to keep a log of which bugs are found with which ctests. This
 way we can see which tests are the most useful. It is difficult to objectively
 differentiate between minor bugs and important bugs.
 
-Examples where convergence tests took time and annoyance to figure out that they
-were actually "false positives" (i.e., no bug that should be fixed):
+Examples where convergence tests took time and annoyance to figure out that
+they were actually "false positives" (i.e., no bug that is worth the time or
+complexity to fix):
 
 https://www.mail-archive.com/search?l=mid&q=20210125200655.e27xaaoy2belyxhw%40tallinn