ctests-costs-benefits: define false positive

[lyx.git] / development / autotests / ctests-costs-benefits.txt

diff --git a/development/autotests/ctests-costs-benefits.txt b/development/autotests/ctests-costs-benefits.txt
index 9d070e725b10ec8aa76948bd476466f7e683f6b8..772770ebb09a88c38640b82c169e5c8c86827a2d 100644 (file)
--- a/development/autotests/ctests-costs-benefits.txt
+++ b/development/autotests/ctests-costs-benefits.txt
@@ -14,3 +14,9 @@ cost, it should be taken into account when we review.
 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 is worth the time or
+complexity to fix):
+
+https://www.mail-archive.com/search?l=mid&q=20210125200655.e27xaaoy2belyxhw%40tallinn