[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CG: add information about Regtest Checking Project (issue 5669047)
From: |
janek . lilypond |
Subject: |
Re: CG: add information about Regtest Checking Project (issue 5669047) |
Date: |
Tue, 14 Feb 2012 22:24:40 +0000 |
http://codereview.appspot.com/5669047/diff/1/Documentation/contributor/regressions.itexi
File Documentation/contributor/regressions.itexi (right):
http://codereview.appspot.com/5669047/diff/1/Documentation/contributor/regressions.itexi#newcode511
Documentation/contributor/regressions.itexi:511: it shouldn't check
everything at once. For example it's a bad idea to test
On 2012/02/14 18:33:06, Graham Percival wrote:
I disagree slightly here: most regtests should only do a single thing,
but a few
(deliberately) test multiple ones.
Yes, a few regtests are engravings of whole pieces. But since they are
rare, the people checking the results of the survey will handle them.
Nevertheless, i rephrased this a bit and added "usually".
http://codereview.appspot.com/5669047/
- CG: add information about Regtest Checking Project (issue 5669047), janek . lilypond, 2012/02/14
- Re: CG: add information about Regtest Checking Project (issue 5669047), graham, 2012/02/14
- Re: CG: add information about Regtest Checking Project (issue 5669047),
janek . lilypond <=
- Re: CG: add information about Regtest Checking Project (issue 5669047), graham, 2012/02/17
- Re: CG: add information about Regtest Checking Project (issue 5669047), janek . lilypond, 2012/02/22
- Re: CG: add information about Regtest Checking Project (issue 5669047), janek . lilypond, 2012/02/25
- Re: CG: add information about Regtest Checking Project (issue 5669047), janek . lilypond, 2012/02/26