Regression testing breakthrough

[Austin English]

On Tue, Oct 18, 2011 at 10:26, Dmitry Timoshkov <dmitry at baikal.ru> wrote:
> Austin English <austinenglish at gmail.com> wrote:
>
>
>> > Reverting a patch in latest git is not always possible, instead it's
>> > a very useful test to revert the patch at the suspected regression point
>> > and see if that really helps.
>>
>> That still doesn't require a full regression test, just:
>> $ git checkout -f $SHA1SUM
>> $ ./configure && make -j4
>> # test
>> $ git show $SHA1SUM | patch -p1 -R
>> $ ./configure && make -j4
>> # retest
>
> How do you know that $SHA1SUM without a regression test?

I was referring to the case you pointed out:
> Moreover, often users get asked 'does reverting commit xxxx' help? Without
> performing a proper regression test it's impossible to asnwer that question.

If a developer asks about a specific commit, then of course you know
which one to try :).

Otherwise, of course a full regression test is required.

-- 
-Austin