Regression testing breakthrough

Damjan Jovanovic damjan.jov at gmail.com
Tue Oct 18 10:45:05 CDT 2011


On Tue, Oct 18, 2011 at 2:32 PM, Dmitry Timoshkov <dmitry at baikal.ru> wrote:

> Henri Verbeet <hverbeet at gmail.com> wrote:
>
> > On 18 October 2011 10:45, Damjan Jovanovic <damjan.jov at gmail.com> wrote:
> > > (especially during "reverse regression testing"), users find it too
> long and
> > > technical, and only a small minority of regressions are ever bisected.
> And
> > Not true. Even for the regressions that are still open it's currently
> > 276 bisected vs. 99 not bisected, and Alexandre said about 90% of
> > opened regressions get fixed.
>
> Moreover, often users get asked 'does reverting commit xxxx' help? Without
> performing a proper regression test it's impossible to asnwer that
> question.
>
>
Reverting a commit in the latest git is just 1 round of
patch+configure+make+run, and reverting to the commit before it in the
binary repository is just one git command. Why would you need a "proper
regression test"?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20111018/71f15741/attachment.html>


More information about the wine-devel mailing list