db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4089) It should be possible to run unit tests right after "ant all"
Date Tue, 10 Mar 2009 15:12:53 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680505#action_12680505
] 

Rick Hillegas commented on DERBY-4089:
--------------------------------------

Hi Aaron and Kristian,

I think that the jar files are a better default than the classpath. I think that the tests
are more meaningful when they run against the production configuration (jar files)--and building
the jar files does not seem like a big burden to me. I would go so far as to say that testing
against the production configuration is the only meaningful barrier to checkin. Some tests
only run against jar files (like the autoloading of the jdbc drivers and the automatic installation
of the network security manager). The production configuration catches tricky packaging issues
in which developers forget to update the build logic to supplement the jars with classes which
are loaded by reflection rather than reference.

> It should be possible to run unit tests right after "ant all"
> -------------------------------------------------------------
>
>                 Key: DERBY-4089
>                 URL: https://issues.apache.org/jira/browse/DERBY-4089
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.4.2.0
>            Reporter: Aaron Digulla
>
> Right now, the property "derby.junit.classpath" is empty by default. There should be
an ant target which sets the correct classpath to run all tests after an initial checkout
and "ant all".
> The current situation is very confusing to beginners and people who try to build Derby
for the first time. For example, when running the tests, I got this exception:
> java.lang.ClassNotFoundException: org.apache.derbyTesting.junit.EnvTest
> but that class was there, the file was there, everything was correct. Googling for the
error didn't turn anything up, either. It took me a while to believe that build.xml just wouldn't
try to setup a classpath for the tests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message