[
https://issues.apache.org/jira/browse/DERBY-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew McIntyre updated DERBY-2305:
-----------------------------------
Attachment: derby-2305-v1.diff
Starting over, decided to just go ahead and include the new BadConnectionTest
this time instead of trying to untangle the two patches.
Comments for BadConnectionTest:
1. I had to get the default connection or else the driver wasn't automatically
loaded via any of the other setup processes. Is that expected?
2. Using clientServerDecorator excludes the test from running on j9, are we not
expecting to run client testing with j9 at all?
3. I probably didn't need to assertEquals the entire exception text in
testBadConnectionAttribute. I can remove that if anyone objects.
> 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.
