On 2016-01-25, Kornel Benko wrote:
> Am 25. Januar 2016 um 21:07:23, schrieb Guenter Milde <mi...@users.sf.net>
>> On 2016-01-25, Kornel Benko wrote:
>> >> > Everything in autotests should compile (not inverted), if not ==>
>> >> > regression.
>> >> Why should we treat "autotests" different from other directories?
>> > I'd like to have a directory for regressions only. ¹
>> Could you move your example file to trac then?
> Why should I copy it each time from trac when I want to check if the
> file compiles? I am not very fond of trac for testfiles.
OK. For non-developers, trac is the only way to publish test files, for
developers there are alternatives...
So, back to a place for failing test samples¹.
Alternatives:
a) keep them local (this is what most developers currently do).
+1 simple, good if you work alone on an issue
-1 no collaboration
b) put to autotests/export/ and add a commented inversion pattern
+1 no need to move the sample once it works
+1 problem description can be seen without opening a lyx file,
at the same place like other todo issues (without dedicated test file)
-1 mix of working and failing files in the sample directory
c) put in a new directory and move once it works
-1 problem description canot be seen without opening the lyx sample
+1 no mix of working and failing files in the sample directory
For c), also the entry
# Probably language mess
export/export/ja/wrong_auto_encoding_(dvi|pdf(|3))
must be removed from suspiciousTests and the file moved.
We should also consider that there are already "autotest" files scattered
at several places:
development/autotests/
autotests/
Testing/ # Logs written to Testing/Temporary/
Suggestions:
* collect the autotest files under one of
Testing/autotests/ or
development/autotests/
* rename (Testing|development)/autotests/export/ to
(Testing|development)/autotests/samples/
* eventually add .../autotests/failing-samples/
or .../autotests/samples/failing/
Add a README in the samples/ and failing(-samples)? directory, explaining
for all to place working samples here and failing samples there.
Günter
¹ mind, that the "longest labeling label" problem is not a *regression* -
is is there from the beginning of LyX (well actually only since the
support for "longest label").
