This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] minimal test case for sha-1 and md5


Tom Tromey writes:
 > >>>>> "Andreas" == Andreas Tobler <toa@pop.agri.ch> writes:
 > 
 > Andreas> My motivation with these two tests was simply not to forget a
 > Andreas> test, we need every single test even if they are small. And
 > Andreas> they would have shown us in gcc world that something has been
 > Andreas> broken.
 > 
 > Often one of us has to rewrite a test case into Mauve form.
 > Library tests really belong in Mauve, not libgcj.  That way they can
 > be shared among all Classpath users.

In this particular case, I want message digest tests in the libgcj
testsuite because they test important system components and are also
an excellent test of the compiler.  Everyone who builds gcc and runs
"make check" gets to run these tests, rather than the three people in
the world who routinely run Mauve.

Sure, add tests to Mauve as well, but it's not an alternative.

Andrew.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]