From 0942948dca35950b6e9cd3529ada31c38360e184 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Janek=20Warcho=C5=82?= Date: Sun, 18 Mar 2012 09:39:36 +0100 Subject: [PATCH] Web: add regtest checking to helpus, final touches --- Documentation/contributor/regressions.itexi | 5 ++++- Documentation/included/helpus.itexi | 5 +++++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/Documentation/contributor/regressions.itexi b/Documentation/contributor/regressions.itexi index 2c7783c1d7..a5dac48226 100644 --- a/Documentation/contributor/regressions.itexi +++ b/Documentation/contributor/regressions.itexi @@ -485,7 +485,9 @@ a small @file{.ly} file demonstrating the problem was added to the regression tests as a proof that the fix works. If someone will accidentally break breve width again, we will notice this in the output of that regression test. -We are asking you to help us by checking a regtest or two from time to time. +@subheading How can I help? + +We ask you to help us by checking one or two regtests from time to time. You don't need programming skills to do this, not even LilyPond skills - just basic music notation knowledge; checking one regtest takes less than a minute. Simply go here: @@ -505,6 +507,7 @@ or @rinternalsnamed{Top, Internals Reference}. Vague descriptions (like "behaves well", "looks reasonable") shouldn't be used. @ignore +this may be useful for advanced regtest checking @subsubheading Is regtest straightforward and systematic? Unfortunately some regtests are written poorly. A good regtest should be diff --git a/Documentation/included/helpus.itexi b/Documentation/included/helpus.itexi index 1578a36174..9aa7be0631 100644 --- a/Documentation/included/helpus.itexi +++ b/Documentation/included/helpus.itexi @@ -29,6 +29,11 @@ Mailing list support: answer questions from fellow users. Bug reporting: help users create proper @rweb{Bug reports}, and/or join the Bug Squad to organize @rcontrib{Issues}. +@item +@rcontrib{Grand Regression Test Checking}: verify that LilyPond works correctly +by examining output of test snippets. Checking one snippet takes less +than a minute! + @item Documentation: small changes can be proposed by following the guidelines for @rcontrib{Documentation suggestions}. -- 2.39.2