This is the mail archive of the
mailing list for the Mauve project.
Re: New Harness, version 1
The README was missing something important.
2006-04-05 Anthony Balkissoon <firstname.lastname@example.org>
* README: Added line about compiling the Harness, RunnerProcess, and
On Wed, 2006-04-05 at 16:19 -0400, Anthony Balkissoon wrote:
> Okay, the new Harness is checked in, please use it and comment on
> features you would like added.
> Running tests is now much easier, please use the harness script in the
> top folder. ./harness -help will print a help message, and the README
> file gives more detailed instructions, but it is very intuitive. Simply
> specify the tests or folders you want to run.
> "./harness javax.swing" will run all the tests in
> It is important to specify the VM you wish to use to run the tests. If
> you always (or almost always) run the Mauve tests using the same VM, you
> should export the environment variable MAUVEVM. For example, I have
> MAUVEVM=jamvm, so the above command would run all the javax.swing tests
> on JamVM. Alternately, you can use the -vm option (say, if you want to
> run against Sun to make sure the tests pass, or just for comparison):
> "./harness -vm PATH-TO-EXECUTABLE" javax.swing"
> This will override the MAUVEVM variable. If neither of these options is
> used, the tests will be run on the system "java" VM, whatever you have
> that set to.
> Comments are greatly appreciated.
> 2006-04-05 Anthony Balkissoon <email@example.com>
> * Harness.java: New file.
> * README: New file (old one moved to README.OldHarness).
> * README.OldHarness: New file, copied from the old README.
> * RunnerProcess.java: New file.
> * harness: New file.
RCS file: /cvs/mauve/mauve/README,v
retrieving revision 1.21
diff -u -r1.21 README
--- README 5 Apr 2006 20:11:27 -0000 1.21
+++ README 5 Apr 2006 21:18:21 -0000
@@ -25,3 +25,10 @@
defaults to `mx10.gnu.org'
(Use this option if your local firewall
blocks outgoing connections on port 25.)
+After configuring, compile (using your favourite java compiler) the files
+Harness.java and RunnerProcess.java.
+Then compile all the tests (or, if you don't plan on running all the tests,
+only the ones you wish to run). This can be done by compiling *.java from
+the gnu.testlet folder. On my machine I did this with the following command:
+find gnu/testlet -name "*.java" | xargs jikes
*******RUNNING THE TESTS*******