This is the mail archive of the
mailing list for the Mauve project.
Re: VM tests [was Re: Library/VM tests]
- To: firstname.lastname@example.org (Artur Biesiadowski)
- Subject: Re: VM tests [was Re: Library/VM tests]
- From: Godmar Back <email@example.com>
- Date: Fri, 12 Mar 1999 09:19:28 -0700 (MST)
- Cc: firstname.lastname@example.org, email@example.com
For a start, we could just use the kaffe/test/regression/TestScript.in
Alexandre Oliva wrote.
It allows compile options and the expected output to be hidden in a
comment in the .java file, runs a test and (optionally) sorts and
diffs the output.
It does not support java assembler, JNI or native tests nor does it
support timeouts. These are all very useful features. It's using sh
at this point, but I wouldn't mind using perl.
> This certainly would reuqire very different handling.
> I think that it can be done by creating some informative directory
> structure and then executing each class in separate VM by command line
> (from makefile or perl or some other script).
> A lot of tests should be written directly in assembler - you cannot be
> sure how compilers will translate given code. With assembler we can test
> verious verify error, some magic combinations of stack/jumps which would
> be impossible from java. This requires java assembler - there are some
> available on the net, with jasmin coming to mind, but it is a bit large
> (450kb packed ?).
> JNI tests would require C compiler and some knowledge about runtime libs
> of given vm. Smart configure script should be enough.
> Some way would have to be defined to kill infinite loops. Maybe second
> process sleeping for few minutes ?