db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dyre Tjeldvoll (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-1977) Let GUI TestRunners run JUnit tests without the -noloading option
Date Tue, 25 Mar 2008 13:47:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Dyre Tjeldvoll updated DERBY-1977:

    Summary: Let GUI TestRunners run JUnit tests without the -noloading option  (was: Make
it possible to run JUnit tests with the GUI runners)

Reopening the issue and changing the summary to better reflect the current situation.

> Let GUI TestRunners run JUnit tests without the -noloading option
> -----------------------------------------------------------------
>                 Key: DERBY-1977
>                 URL: https://issues.apache.org/jira/browse/DERBY-1977
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Dyre Tjeldvoll
> Kristain Waagan wrote in a message on derby-dev:
> > The problem is that the GUI runners are using a custom classload to
> > allow for dynamic reloading of the test classes. It defeats the getURL
> > method in SecurityManagerSetup, seemingly by returning an empty/null
> > (the object itself isn't null) ProtectionDomain object. This finally
> > leads to the URL object extracted being null, which causes the NPE.
> >
> > A workaround is to specify the -noloading option for the runner, like this:
> > java -classpath X junit.swingui.TestRunner -noloading
> > org.apache.derbyTesting...
> >
> > If you do this, you must restart the GUI if you recompile the test classes.
> > We should investigate this and see if we can get it working without
> > specifying the -noloading argument.

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

View raw message