Rick Hillegas wrote:
Hi Dan,
I was hoping that the first point could be accomplished by some
jiggery pokery which ran the compatibility suite under the normal
(non-junit) test harness, producing a canon. This wouldn't wrench the
existing machinery around too much. However, it would require
developers to download the junit jar so that the test class would
build and execute...and this may be controversial.
I don't think that the existing harness *requires* output to a canon,
does it? I was working on a unit test for exceptions which produced no
output, and as long as I had an empty master file the test harness was
satisfied.
begin:vcard
fn:David W Van Couvering
n:Van Couvering;David W
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
