From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Wilkinson To: mauve Subject: Library/VM tests Date: Tue, 02 Mar 1999 16:06:00 -0000 Message-id: <36DC7DA9.16A46D4F@transvirtual.com> X-SW-Source: 1999-03/msg00000.html I have (finally) been looking into integrating our modest testsuite into Mauve but have run up against a problem. So far as I understand things Mauve is designed to test *only* the library functionality. Given this what are we suppose to do about test which sit on the boundary - ClassLoaders spring to mind but there's also such things as Serialization, Reflection and bunch of other borderline stuff. None of this is VM specific of course but it relies on more heavy VM support than some tests (some stuff uses threads for example). So my question is - what's the policy on this? Cheers Tim -- Tim Wilkinson Tel: +1 510 704 1660 Transvirtual Technologies, Inc., Fax: +1 510 704 1893 Berkeley, CA, USA. Email: tim@transvirtual.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Wilkinson To: mauve Subject: Library/VM tests Date: Thu, 01 Apr 1999 00:00:00 -0000 Message-ID: <36DC7DA9.16A46D4F@transvirtual.com> X-SW-Source: 1999-q1/msg00016.html Message-ID: <19990401000000.Yo92dGNxoReMrZoVNbNFXcSyUJ-3xEwTf85Ny9s6Z98@z> I have (finally) been looking into integrating our modest testsuite into Mauve but have run up against a problem. So far as I understand things Mauve is designed to test *only* the library functionality. Given this what are we suppose to do about test which sit on the boundary - ClassLoaders spring to mind but there's also such things as Serialization, Reflection and bunch of other borderline stuff. None of this is VM specific of course but it relies on more heavy VM support than some tests (some stuff uses threads for example). So my question is - what's the policy on this? Cheers Tim -- Tim Wilkinson Tel: +1 510 704 1660 Transvirtual Technologies, Inc., Fax: +1 510 704 1893 Berkeley, CA, USA. Email: tim@transvirtual.com