Hello, It seems that the following should be done to include Jasmin tests into the infrastructure: - support different types of files in the test suite - at least Java and Jasmine. It may be not a good idea to create a separate test suite for Jasmine tests because a developer that creates test for some functionality would have to switch between them if he/she wants to write tests partly in Java partly in Jasmine. Maybe someone would want to create a test with mixed Java and Jasmine code - for example, test written in Java that loads class compiled from Jasmine - such test may be not only smoke/unit but also stress, performance, etc - like tests written in Java - test harness should be able to support not only common JUnit/TestNG/... classes but also things like negative class loading tests - there are classes with broken structures and the test is an attempt to load them - if JVM fails, the test passes.
On 8/2/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
I was looking at HARMONY-788 today, and I'd like to be able to incorporate some of the jasmin tests into our infrastructure. I presume that the techniques for creating arbitrary class files will be useful for classlib as well? Anyone have any thoughts on how we might go forward here, in DRLVM anyway? I don't want to keep going w/ the current tests (a la smoke). geir --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Regards, Anton Luht, Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
