[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] auto generated regression tests

From: Evan Berggren Daniel
Subject: Re: [gnugo-devel] auto generated regression tests
Date: Sun, 4 Aug 2002 12:27:44 -0400 (EDT)

On Sun, 4 Aug 2002 address@hidden wrote:

> > attached are a collection of games and regression tests.  They all are
> > based on matcher_status inconsistencies from the script.
> > Expected passes are marked relative to gnugo 3.2, however gnugo 3.3.5
> > gains at least one test.  Some of these I have analyzed and put in checks
> > on owl_attack, etc, but most are just based on dragon_status.  I'm not
> > sure all the tests are correct (I may have read things wrong), so someone
> > else should probably look them over.
> As a general comment, the dragon_status is not a very important
> field. Probably these tests should be in terms of either
> matcher_status or owl tests. The dragon status is a very
> rough approximation which is superceded by the owl status
> if the owl status is not UNCHECKED. So the dragon status
> can be wrong and the owl status correct, and we don't
> care about such cases.

OK.  I'll add a matcher_status check command for a single vertex next.
However, it should be noted that the matcher_check script, which generated
all the places with inconsistencies, is based on the matcher_status field.
I just used the dragon_status for regression since there didn't seem to be
anything better.

Also, in many of the cases, owl_does_attack foo bar will return true, but
owlattack bar fails to find any attacks.  I only went and found these for
some of the tests, but I think there are more in the games I sent.
The same is true for owl_defend.


Evan Daniel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]