[
https://issues.apache.org/jira/browse/DERBY-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471104
]
Daniel John Debrunner commented on DERBY-2305:
----------------------------------------------
A1) Yes.
A2) Client doesn't implement JSR169 so it cannot be run on J2ME/CDC/Foundation
A3) Comparing the exception text means that the test will most likely fail if
run in a different locale.
It would be good to have the ability to run the tests in different locales :-)
Also it seems nothing in BadConnectionAttribute is specific to client/server.
Seems like moving the test to jdbcapi and renaming the class
ConnectionAttributeTest would be good. Then it could be a single place for
checking bad and good attributes, combining with checkDriver.
> 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.
