Regtests
From LilyPond Wiki
The regression tests (Regtests) are located in input/regression.
Alternatively, you may find them on this web page.
Here's a full review of the regtests, started on March 4 2010. (version 2.13.15)
The page has been arranged so that issues that appear not to be "documentation issues" or have been fixed are on another page, for ease of tracking. Please see these pages:
If you fix an issue, please feel free to delete it from this page, having copied it to the relevant other page (having 2 windows open at once makes this easy).
[edit] Unfixed documentation issues
[edit] accidental-tie-overriden.ly
-> snippet?
- This throws errors and doesn't produce the right output in 2.12.3 and so I reckon it can't be added to the LSR yet. It could be added once 2.13 is released and the LSR upgraded. --PhilHolmes 18:28, 27 June 2010 (UTC)
- this works in 2.13.24 so I'll add a snippet to the NR: Jlowe 10:34, 2 July 2010 (UTC)
- Patch submitted:Jlowe 11:45, 3 July 2010 (UTC)
- James, the snippet looks fine, but there's a pitfall you must be sure to avoid: the file name must be the same as the doctitle (with hyphens, of course), otherwise once it's added to LSR following a version bump the file name will change, leading to docs compilation failure. --NeilP 14:10, 4 July 2010 (UTC)
- Patch submitted:Jlowe 11:45, 3 July 2010 (UTC)
- this works in 2.13.24 so I'll add a snippet to the NR: Jlowe 10:34, 2 July 2010 (UTC)
[edit] ambitus-gap.ly
-> snippet?
- I'll sort one out for this, since I'm responsible for adding the property.NeilP 23:12, 9 March 2010 (UTC)
[edit] chord-scripts.ly
-> I can't find where the ability to attach articulations to notes /inside/ < ... > constructs is documented.
- How about showing-the-same-articulation-above-and-below-a-note-or-chord.ly? NeilP 23:20, 9 March 2010 (UTC)
- There are a couple of bugs associated with this - the regtest is wrong and the behaviour doesn't respect requests for above/below the line. Waiting for these to be fixed before doing more on this one. --PhilHolmes 14:38, 1 July 2010 (UTC)
- The bugs have been fixed for 2.13.27. I have an emended snippet to add to snippets/new which I'll push once I can do a full LSR update (LSR's down at the moment.) --NeilP 14:14, 4 July 2010 (UTC)
- I have updated the NR in a few places where chords are mentioned (Chord Mode, Chord Repetition and Chorded Notes in general) - patch submitted to Trevor:Jlowe 10:44, 27 July 2010 (UTC)
- Patch Pushed commits c8919b52092cc6b1f39ba638d9fc8f179ac32d71 and 599d7f96e9bd01517f42d0e6c1bcb446f5899bd7:Jlowe 04:29, 28 July 2010 (UTC)
- I have updated the NR in a few places where chords are mentioned (Chord Mode, Chord Repetition and Chorded Notes in general) - patch submitted to Trevor:Jlowe 10:44, 27 July 2010 (UTC)
- The bugs have been fixed for 2.13.27. I have an emended snippet to add to snippets/new which I'll push once I can do a full LSR update (LSR's down at the moment.) --NeilP 14:14, 4 July 2010 (UTC)
- There are a couple of bugs associated with this - the regtest is wrong and the behaviour doesn't respect requests for above/below the line. Waiting for these to be fixed before doing more on this one. --PhilHolmes 14:38, 1 July 2010 (UTC)
[edit] clef-oct.ly
-> snippet?
- I think this could be incorporated into the existing text. NeilP 23:20, 9 March 2010 (UTC)
- Seems pretty clear to me in the docs already. The NR, Section 1.1.3 says "By adding _8 or ^8 to the clef name, the clef is transposed one octave down or up, respectively, and _15 and ^15 transpose by two octaves. The clef name must be enclosed in quotes when it contains underscores or digits." What more needs adding to the docs? --PhilHolmes 16:32, 20 May 2010 (UTC)
- The docs don't mention that arbitrary values can be used (e.g, _2, ^11) --NeilP 22:01, 10 June 2010 (UTC)
- This has been rectified. Arbitrary values have now been documented. Commit 42d36ea50b7ba80ea326e4d17bb1af02ad9f994f Thu, 17 Jun 2010 17:59:39 - JL
- Reckon this is also worth a snippet in the LSR. I'll do. --PhilHolmes 11:06, 27 June 2010 (UTC)
- Done. http://lsr.dsi.unimi.it/LSR/Item?id=695 --PhilHolmes 15:38, 5 July 2010 (UTC)
[edit] dot-dot-count-override.ly
-> snippet?
- Done. --PhilHolmes 10:52, 21 May 2010 (UTC)
- Only problem is that \override Dots #'dot-count doesn't work on the LSR - it does work on 2.12.3. GP thinks it may have been a change from 2.12.2 to 2.12.3. Anyway, here's a snippet for the LSR. I originally added this to the LSR but have deleted it since it doesn't work... --PhilHolmes 15:30, 26 May 2010 (UTC)
\relative c {
c4.. a16 r2
\override Dots #'dot-count = #4
c4. a8 r2
\override Dots #'dot-count = #0
c4.. a16 r2
\revert Dots #'dot-count
c4.. a16 r2
}
- I am working on this - it's my first attempt to patch with a new ../new/snippet/.. included in it so bear with me. I'll update when it has been submitted: Jlowe 18:45, 27 June 2010 (UTC)
- Patch has been accepted and pushed: Jlowe 17:29, 29 June 2010 (UTC)
[edit] double-repeat-default-volta.ly
-> snippet?
- Another one of mine. Will add a snippet. NeilP 23:32, 9 March 2010 (UTC)
[edit] dynamics-context-textspan.ly
-> the Dynamics context is undocumented.
- Looks like a feature of 2.13? Will do a snippet when the LSR is at 2.13/14. Since it looks like quite an update for the later version, I presume there will be documentation in the NR? --PhilHolmes 15:50, 5 July 2010 (UTC)
[edit] dynamics-custom-text-spanner-postfix.ly
-> postfix dynamics are undocumented.
- Add snippets/dynamics-custom-text-spanner-postfix.ly as selected snippet? NeilP 23:32, 9 March 2010 (UTC)
- See dynamics-context-textspan.ly - I believe this is the same. --PhilHolmes 15:52, 5 July 2010 (UTC)
[edit] dynamics-hairpin-length.ly
-> this specific behavior should be documented (plus, it's generally good musical practice to not leave a hairpin without an explicit dynamic...)
- Related snippet: hairpin-neighboring-span-dynamics.ly
- Setting 'bound-padding changes the space between the items, but it's scaled down for adjacent hairpins by a factor of three. NeilP 23:38, 9 March 2010 (UTC)
[edit] dynamics-text-spanner-postfix.ly
-> ditto: postfix dynamic spanners are undocumented.
- Add snippets/dynamics-text-spanner-postfix.ly as selected snippet? NeilP 23:32, 9 March 2010 (UTC)
[edit] flags-in-scheme.ly
-> undocumented. Snippet?
[edit] flags-straight-stockhausen-boulez.ly
-> Undocumented. flag-styles should be documented like accidental-styles, or ideally flag-styles.scm should even generate its own documentation.
[edit] font-postscript.ly
make-century-schoolbook-tree is absolutely undocumented. (what's it for anyway?)
- This just seems to show how to change the default font used for text markups. This is absolutely documented here
http://lilypond.org/doc/v2.13/Documentation/notation/fonts. I don't think this needs to be added:Jlowe 16:07, 14 July 2010 (UTC)
[edit] fret-diagrams-origin.ly
fret-diagrams-landscape.ly, fret-diagrams-opposing-landscape.ly Diagrams orientation is only documented through the fret-diagrams-explained-and-developed.ly snippet. This snippet should be explicitly included in NR 2.4.1 (rather than merely dumped in the snippet list).
- I'll add this snippet. However it is not clear why the other *.ly reg tests were mentioned. Did you want to include them too?:Jlowe 15:46, 14 July 2010 (UTC)
[edit] lyric-hyphen.ly
-> This looks a mess. The main feature lines are commented out and the aim of the regtest isn't clear.
- If it can be sorted out, I'd do a snippet. --PhilHolmes 17:46, 22 May 2010 (UTC)
- Are you looking at a different test? I can't see any issues with this. --NeilP 21:24, 10 June 2010 (UTC)
- Well it seems to me that 'half' the example is missing compared to the lilypond ly file. That is the 'x - - y' part is not showing on the reg tests. Is that significant?:Jlowe 15:48, 14 July 2010 (UTC)
[edit] markup-eyeglasses.ly
-> Think this was a joke and needs deleting? --PhilHolmes 17:52, 22 May 2010 (UTC)
- No joke. --NeilP 21:42, 10 June 2010 (UTC)
- This is already documented - http://lilypond.org/doc/v2.13/Documentation/notation/other:Jlowe 16:19, 14 July 2010 (UTC)
[edit] trill-spanner-chained.ly
-> Shows how trills automatically stop when a new one starts. Can't find this documented. It works on 2.12.3 on my PC, but not on the LSR, so snippet is below:
\relative c {
g8 f\startTrillSpan
f8 g\startTrillSpan
g8 r\stopTrillSpan r4
\override TrillSpanner #'to-barline = ##t
c1\startTrillSpan
\revert TrillSpanner #'to-barline
\override TrillSpanner #'(bound-details right padding) = #1.2
c1\startTrillSpan
\revert TrillSpanner #'(bound-details right padding)
c1\startTrillSpan
c1\startTrillSpan
}
