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 14:26:09 GMT

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

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

I looked at running LobStreamsTest with a different encoding a while back and couldn't figure
out a way to do it. 

The java property file.encoding is reporting the encoding of the current platform, not to
be used to set the encoding in use.

I think the only official way to do this may be to run all the tests on two different machines
with different encodings setup at the operating system level.

> 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