| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
We have a huge directory of regression tests. Checking the regtests is a huge chore, but it’s also desperately important for stable releases by identifying Critical bugs as soon as they occur. Let’s split them up somewhat.
Similarly, there is a discrepancy between our stated policy on adding regtests, and our actual practice in handling bugs and patches. When should we add regtests? If we do it for every single bug, then the poor fellow(s) checking the regtests will just give up like they did back in the 2.13 days; that results in a very counter-productive test framework.
We have a bunch of regtests which are only added to make sure that lilypond doesn’t crash. We don’t need to look at the graphical output of those.
We have a bunch of regtests whose only purpose is to produce console output. We don’t need to look at the graphical output of those.
not yet.
None yet, but it’ll be a mess.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated by Graham Percival on June 13, 2012 using texi2html 1.82.