| [ << Regression tests ] | [Top][Contents][Index][ ? ] | [ Programming work >> ] | ||
| [ < Regression tests ] | [ Up : Regression tests ] | [ Precompiled regression tests > ] | ||
9.1 Introduction to regression tests
LilyPond has a complete suite of regression tests that are used to ensure that changes to the code do not break existing behavior. These regression tests comprise small LilyPond snippets that test the functionality of each part of LilyPond.
Regression tests are added when new functionality is added to LilyPond. We do not yet have a policy on when it is appropriate to add or modify a regtest when bugs are fixed. Individual developers should use their best judgement until this is clarified during the Grand Organization Project (GOP).
The regression tests are compiled using special make
targets. There are three primary uses for the regression
tests. First, successful completion of the regression tests means
that LilyPond has been properly built. Second, the output of the
regression tests can be manually checked to ensure that
the graphical output matches the description of the intended
output. Third, the regression test output from two different
versions of LilyPond can be automatically compared to identify
any differences. These differences should then be manually
checked to ensure that the differences are intended.
Regression tests (“regtests”) are available in precompiled form as part of the documentation. Regtests can also be compiled on any machine that has a properly configured LilyPond build system.
| [ << Regression tests ] | [Top][Contents][Index][ ? ] | [ Programming work >> ] | ||
| [ < Regression tests ] | [ Up : Regression tests ] | [ Precompiled regression tests > ] | ||