db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-5771) Use TestNullOutputStream where possible
Date Wed, 23 May 2012 10:05:41 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen closed DERBY-5771.
-------------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
    Issue & fix info:   (was: Patch Available)

Thanks, Kristian. Committed revision 1341814.
                
> Use TestNullOutputStream where possible
> ---------------------------------------
>
>                 Key: DERBY-5771
>                 URL: https://issues.apache.org/jira/browse/DERBY-5771
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Trivial
>             Fix For: 10.9.0.0
>
>         Attachments: d5771-1a.diff
>
>
> Derby's test framework provides a stream class, TestNullOutputStream, that discards all
data written to it. Utf8CcsidManagerClientTest's constructor and BaseJDBCTestCase.runScript()
create their own anonymous classes that provide the same functionality. They should be changed
to reuse TestNullOutputStream.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message