This is the mail archive of the
mailing list for the Mauve project.
- To: mauve-discuss at sources dot redhat dot com
- Subject: simple tests
- From: Brian Jones <cbj at gnu dot org>
- Date: 07 Feb 2001 23:12:53 -0500
I'm seeking an opinion on how I might write a test for java.io.File
that actually tests everything. I'm wondering specifically how well I
can test setting/getting last modified time on a given file without
verification from second program, and what to do about listRoots() as
well. I think I can get around some of this by making assumptions
about the machine I run the test on, but that doesn't seem like the
right thing to do with respect to mauve.
Would it be useful to make a two pass harness of sorts... the first
pass could test development and the second could be from something
more stable (like the JDK) providing verification?
Brian Jones <firstname.lastname@example.org>