db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vemund Østgaard (JIRA) <j...@apache.org>
Subject [jira] Updated: (DERBY-3156) Convert testing of derby error stream to JUnit
Date Fri, 02 Nov 2007 15:18:50 GMT

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

Vemund Østgaard updated DERBY-3156:

    Attachment: 3156-diff

This patch removes the old lang/errorStream.java and lang/logStream.java tests from derbylang.runall,
so they will no longer be run as part of the old harness testing. I have not removed the test

A new test, ErrorStreamTest, is added that runs in the JUnit framework. 
Feeling that this test didn't really belong in the "lang" suite in the first place, I've created
a new suite named "engine" for this test and added this suite to the AllPackages suite that
is run as part of suites.All. I don't have any strong feelings about where the test really
belongs, but from my limited knowledge of the testing this seemed to make most sense.

The new test runs only in the embedded environment. When I ran it in a networkServer environment
it failed with a problem that I logged as a new Jira DERBY-3170. I don't think the bug will
have a high priority so I've submitted this version of the test running only in the embedded
environment so it will not fail.

> Convert testing of derby error stream to JUnit
> ----------------------------------------------
>                 Key: DERBY-3156
>                 URL: https://issues.apache.org/jira/browse/DERBY-3156
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Vemund Østgaard
>            Assignee: Vemund Østgaard
>            Priority: Minor
>         Attachments: 3156-diff, 3156-diff.stat
> Convert the tests that are related to derby error stream properties and functionality.
> Seems to be these two tests:
> lang/logStream.java 
> lang/errorStream.java

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

View raw message