Allen Akin wrote:
On Thu, Jul 01, 2004 at 12:51:23PM +0900, Sasayama wrote:
| Two more questions. First, is it clear on what is covered by each test
| of glean?
Each test includes a description of what it's intended to do. Those are
fairly detailed for some tests, but not for others; it depends on what
the author of the test decided to write. I've appended a log of a glean
run with the "verbose" option enabled, which includes all the
descriptive text.
| Second, is it easy to examine the output correctness of each test in
| glean? It is very nice if it could make a summary report automatically.
Glean produces a summary, but I'd be the first to admit that it needs to
be more readable. The intent is that you should be able to grep the
summary for the word "FAIL" to find any failures.
Glean also has the ability to compare the results of two runs, so if
you're developing an OpenGL implementation you can see if a change has
fixed an old problem or introduced a new one.
I think you'll find that the tests in glean don't cover everything you
need, but it may be helpful as part of whatever testing system you
finally decide to use. And of course, if you want to contribute tests,
that would be much appreciated by everyone.
Thank you. I'll take a look into glean.
begin:vcard
fn;quoted-printable:=E7=AC=B9=E5=B1=B1
n;quoted-printable:=E7=AC=B9=E5=B1=B1
email;internet:[EMAIL PROTECTED]
x-mozilla-html:TRUE
version:2.1
end:vcard
