Commit Graph

27 Commits

Author SHA1 Message Date
Scott Kostyshak
1e58d5cd4a ctests: log fix for an upstream LaTeX2e issue 2022-06-10 09:16:55 -04:00
Scott Kostyshak
81fbada4df ctests: log a ModernCV issue with LaTeX2e pre-rel
ModernCV currently fails with the LaTeX2e pre-release that is
expected to be released very soon.

There is a pull request with a fix that will hopefully be merged
before the new release.
2022-06-10 09:16:05 -04:00
Scott Kostyshak
5f8ba9387d ctests: log a confirmed upstream LaTeX2e issue 2022-05-31 14:21:03 -04:00
Scott Kostyshak
d01f1428be ctests: log a fixed issue 2022-03-12 07:43:54 -05:00
Scott Kostyshak
23b7b95e68 ctests: log fixed upstream Polyglossia issues
Thanks to Jürgen for fixing the upstream issue.

Also add a row "ctest" to give the pattern of the ctests that
failed.
2022-02-16 22:07:05 -05:00
Scott Kostyshak
52c4ff290b ctests: log a fixed issue 2022-02-07 22:13:37 -05:00
Scott Kostyshak
9185fb8ccc ctests: log a fixed issue 2022-02-06 08:13:12 -05:00
Scott Kostyshak
b461d07b5b ctests: log a fixed issue (fr Linguistics.lyx) 2021-12-08 23:04:24 -05:00
Scott Kostyshak
2713ea5189 ctests: log fixed upstream polyglossia issues
Thanks to Jürgen for fixing these upstream Polyglossia regressions.
2021-12-07 13:05:52 -05:00
Scott Kostyshak
d4678a734a ctests: log a fixed issue 2021-12-05 22:07:06 -05:00
Scott Kostyshak
2dd9e1a338 ctests-costs-benefits: add a "benefit" row
The "benefit" row gives the amount of days in-between when an issue
is found because of the ctests and when an issue is reported by
someone not using the ctests. In the example of the ps2pdf flag, the
issue was reported just a couple of weeks after we found it with the
ctests, indicating that the ctests were not that helpful in this
case.
2021-06-21 12:57:38 -04:00
Scott Kostyshak
ef05c951ca ctests: log a reported issue (the ps2pdf flag)
We are still not sure how to fix things to make them more easy for
the user.
2021-06-21 12:56:37 -04:00
Scott Kostyshak
37bce91a8b ctests: log a fixed LaTeX package issue (noweb) 2021-06-20 00:05:42 -04:00
Scott Kostyshak
e0a12aa3a7 ctests: log a fixed issue 2021-05-28 10:35:47 -04:00
Scott Kostyshak
a2bdda5209 ctests: log a fixed issue 2021-05-26 01:21:09 -04:00
Scott Kostyshak
3ffd06fef4 ctests: log a fixed issue 2021-04-23 23:55:56 -04:00
Scott Kostyshak
4cc38f19ee ctests: log a fixed issue 2021-04-10 12:17:36 -04:00
Scott Kostyshak
cf5f4c2061 ctests: for log, specify benefit is quick fixes
In the cost/benefit log, most of the bugs would have been discovered
eventually. The benefit of a test suite is to find bugs quickly.
2021-03-06 20:09:32 -05:00
Scott Kostyshak
cecbf5f096 ctests: log a fixed issue 2021-03-06 20:09:24 -05:00
Scott Kostyshak
279cfb9162 ctests: log a fixed issue 2021-02-19 19:19:53 -05:00
Scott Kostyshak
3c16d627da ctests: log a fixed issue 2021-02-08 00:13:45 -05:00
Scott Kostyshak
7d2c80d0ef ctests: log a fixed issue 2021-02-05 22:45:14 -05:00
Scott Kostyshak
ca6051d148 ctests: log found regression and fix 2021-01-28 13:38:17 -05:00
Scott Kostyshak
9d3dcdc1f7 ctests: add found regression and fix 2021-01-28 00:27:45 -05:00
Scott Kostyshak
a660ed24dc 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.
2021-01-28 00:27:45 -05:00
Scott Kostyshak
a3f591d61e ctests: log cost of recent false positive 2021-01-26 13:29:23 -05:00
Scott Kostyshak
d3065ceeb3 Start a log file to track benefit/costs of ctests
The ctests are not convenient tests. In this file we can attempt to
log the benefits and costs to using them so we can periodically
evaluate which tests we should keep and which we should get rid of.
2021-01-26 13:21:08 -05:00