[
https://issues.apache.org/jira/browse/DERBY-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471109
]
Andrew McIntyre commented on DERBY-2305:
----------------------------------------
Thanks for the quick feedback, Dan.
I guess I was a little surprised when the base test classes didn't load the
driver in their setUp, but I suppose that makes sense if you want to test
different driver loading behaviors and still use the base classes. I asked
about j9 because badConnection was listed in j9derbynetmats.runall, so some
client/server tests were at one time run with j9, however inappropriate that
may have been. :-)
Good point about the exception text. I'll remove that, and take a look at
checkDriver as well...
> Convert tests in derbynet that will run via HarnessJavaTest
> -----------------------------------------------------------
>
> Key: DERBY-2305
> URL: https://issues.apache.org/jira/browse/DERBY-2305
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Andrew McIntyre
> Assigned To: Andrew McIntyre
> Priority: Trivial
> Fix For: 10.3.0.0
>
> Attachments: derby-2305-v1.diff
>
>
> I was able to convert three tests in derbynet to run via HarnessJavaTest. The
> problems with the other tests are mentioned in the javadoc for the test.
> Forking the VM seemed to be a problem in most cases, at least running from
> within Eclipse, because the forked VM would not have the correct classpath.
> Attaching patch for review. Note that BadConnectionTest is commented out in
> _Suite in this patch, as I have a separate patch for converting the very
> simple bad connection test.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
