This is the mail archive of the
mailing list for the Mauve project.
Re: Library/VM tests
>>>>> "Tim" == Tim Wilkinson <email@example.com> writes:
Tim> I guess I wasn't thinking of testing the basic operations of the
Tim> VM - but when it comes down to it they should be tested too don't
Tim> you think - after all they have to work correctly too right?
Tim> Perhaps the testsuite should be split into various sub-trees
Tim> contains test designed to go after particular bits of the Java
Tim> implementation - you could put array[-1] in the tests designed to
Tim> check the VM in one area and leave the API tests in another.
This sounds good to me.
Tim> For such things as serialization I'm not sure what the best
Tim> structure would be - arguably you can serialize any class (even
Tim> ones which don't implement Serializable have a behaviour that can
Tim> be checked) - perhaps you just put a serializable check in each
Tim> class test directory, or maybe you lump the serialization
Tim> together (I'd go for the first option).
This sounds good too. We just need to mark such tests with some kind
of serialization-specific tag.
Is there anybody who is *against* expanding Mauve to include VM tests?
If not, then we should go ahead and talk about requirements and