db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2446) Remove notion of the old test harness from TestConfiguration
Date Mon, 12 Mar 2007 15:46:09 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480128
] 

Daniel John Debrunner commented on DERBY-2446:
----------------------------------------------

My guess on the old harness is that's broken but I don't know how. It's possibly one of:

  - the default encoding is not changed by setting file.encoding
  - the jvm is made inconsistent internally due to setting file.encoding
  - it just happens to work in some vms

I don't think it has anything to do with running in a separate JVM, file.encoding is not for
use in setting the jvm's locale.
See Sun's java bug 4163515

Btw, I see three JUnit  tests still being run under the old harness, not just LobStreamsTest

>grep junit *.runall
derbynetclientmats.runall:junitTests/derbyNet/CompatibilityTest.java
encodingTests.runall:jdbcapi/LobStreamsTest.junit
jdbc40.runall:jdbc4/AutoloadBooting.junit

Also see DERBY-1952

> Remove notion of the old test harness from TestConfiguration
> ------------------------------------------------------------
>
>                 Key: DERBY-2446
>                 URL: https://issues.apache.org/jira/browse/DERBY-2446
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions: 10.3.0.0
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>            Priority: Minor
>
> TestConfiguration has a notion of the old test harness. It is used when the old harness
is running JUnit tests, and differs mostly by reading the system properties set by the harness
and propagating these to the test configuration.
> I found only one JUnit test being run from the harness; LobStreamsTest.junit. However,
this is also run by the JUnit suite jdbcapi.
> My suggestion is to remove the code related to the old harness in TestConfiguration and
disable LobStreamsTest in derbynetclientmats.
> A quick test showed that only LobStreamsTest failed when removing all the relevant code
in TestConfiguration (ran both derbyall and suites.All).

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


Mime
View raw message