Debian Codegraph @

mysql-test/suite/optimizer_unfixed_bugs/README.txt

raw
1 Putting testcases here
2 ~~~~~~~~~~~~~~~~~~~~~~
3
4 When you work on re-verifying or re-classifying a bug (not fixing it),
5 it's a good idea to put the mtr-parsable '.test' testcase here.
6 Benefits:
7 1) tests downloaded from the bugs db are sometimes close to
8 mtr-parsable but not completely (for example if they contain
9 /* comment */); when you re-verify or re-classify you run the test so
10 may have to make it mtr-parsable; if you then put it in this suite,
11 the developer who will work on this bug in a few weeks or months will
12 not have to re-do the same download&fix, she/he can instead reuse your
13 work.
14 2) Others can see how their own work influences many unsolved
15 bugs, by running this suite. If they find that they fix a bug in this
16 suite, we won't later wonder "how come this bug doesn't happen
17 anymore, what fixed it?".
18 3) One can also run this suite with certain switches to see how they
19 influence unsolved bugs:
20 ./mtr --suite=optimizer_unfixed_bugs \
21 --mysqld=--optimizer_switch="firstmatch=off"
22
23 Adding tests to this suite
24 ~~~~~~~~~~~~~~~~~~~~~~~~~~
25 One test file per bug, named bugNNNNN.test.
26 Put the correct (not current and buggy) result file in r/, so that "[ pass ]"
27 in mtr will mean that a bug looks like fixed.
28 When you have fixed a bug, remove files from this suite.
29 t/bug45219.test is an example.