db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-3653) Convert datetime.sql to JUnit
Date Tue, 26 Aug 2008 21:32:44 GMT

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

Myrna van Lunteren resolved DERBY-3653.

    Resolution: Fixed

I committed Junjie's patch with revision 689237 with one change:
I let the test accept, with comment, the difference Junjie found in behavior between Embedded
and DerbyNetClient (see DERBY-3856).

I ran the old datetime.sql test with DerbyNetClient and it too showed the behavior difference
- the test was just not run with DerbyNetClient before so the difference was not noticed.

The rest of the test looked fine to me and suite.All passed.

> Convert datetime.sql to JUnit
> -----------------------------
>                 Key: DERBY-3653
>                 URL: https://issues.apache.org/jira/browse/DERBY-3653
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions:
>            Reporter: Tiago R. Espinha
>            Assignee: Junjie Peng
>            Priority: Minor
>             Fix For:
>         Attachments: derby-3653-1.patch, derby-3653-1.stat
> Converting the existing SQL test to JUnit, using the SQLToJunit tool.

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

View raw message