[
https://issues.apache.org/jira/browse/DERBY-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581870#action_12581870
]
Kristian Waagan commented on DERBY-1977:
----------------------------------------
I don't think this has been fixed as such, we just use the mentioned workaround
(using the -noloading option).
Maybe "Won't fix" would be a better resolution?
> Make it possible to run JUnit tests with the GUI runners
> --------------------------------------------------------
>
> Key: DERBY-1977
> URL: https://issues.apache.org/jira/browse/DERBY-1977
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> 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.
