db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <Richard.Hille...@Sun.COM>
Subject Re: Features of the JUnit test execution harness
Date Wed, 25 Jan 2006 23:34:37 GMT
Hi Deepa,

Thanks for bringing this up. I agree that being able to run JUnit tests 
on the small device configuration would be a good idea.


Deepa Remesh wrote:

>>One thing that would be great is if there was a well defined  way to
>>have tests handle jvm specific, framework specific or version specific
>>logic, since there will have to be some replacement for the many
>>properties in the test harness and the individual test checks for
>>framework that we have now.
>I would also like to know how JUnit tests will map the current test
>harness properties. My concern is specifically how to run JUnit tests
>with CDC/Foundation/jsr169. I found the following test failing in this
>environment: derbyall/derbyall.fail:junitTests/lang/LangSuite.java
>The reason is the test uses DerbyJUnitTest.getConnection method which
>uses Driver class which is not available in jsr169. For tests which
>use the current test harness, ij.startJBMS() method is used to get
>connections which handles getting connection on different platforms.
>Can we have a similar central method to get connections in the JUnit
>I think it would be good to get JUnit tests running in this
>environment before we move more tests.

View raw message