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
Anton,
- 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.
In other words you suggest we should
Anton Luht wrote:
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
In other words you suggest we should develop our own harness, right? :)
At least search for existing harnesses - I'm sure there are projects
with tests in mixed nature (languages, way of execution, etc) with
test infrastructure that runs them all and displays results in an
uniform manner.
--
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
