From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Tromey To: Tim Wilkinson Cc: Artur Biesiadowski , mauve Subject: Re: Library/VM tests Date: Thu, 01 Apr 1999 00:00:00 -0000 Message-ID: <87n21jrwv8.fsf@cygnus.com> References: <36DC7DA9.16A46D4F@transvirtual.com> <36DE6CCC.83CF838B@pg.gda.pl> <36DF49FC.DE96ADD8@transvirtual.com> X-SW-Source: 1999-q1/msg00024.html Message-ID: <19990401000000.vclsa_Sn6ELQG0c1E6eO1af5vvNdAZLYz_kl_W8Lubs@z> >>>>> "Tim" == Tim Wilkinson 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? I agree. 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 implementation. Tom