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-2656) Run suites.All against a collated database
Date Wed, 11 Jul 2007 19:59:04 GMT

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

Daniel John Debrunner commented on DERBY-2656:

Or a bug was introduced after you ran the tests, or a new test case was added ...

Rather than a one-off (two-off) task, I wonder if we could make this repeatable by adding
more existing tests into the CollationTest.
Adding the DatabaseMetaDataTest is a good choice because meta data is where we know there
might be issues given the different collations.
Are there any other potential areas that could be covered by existing tests?

E.g. testing of the math funtions (sin cos etc.) is very unlikely to be affected by collation
so little benefit in adding that test case but what about others?

> Run suites.All against a collated database
> ------------------------------------------
>                 Key: DERBY-2656
>                 URL: https://issues.apache.org/jira/browse/DERBY-2656
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
>             Fix For:
>         Attachments: DERBY-2656_diff.txt
> It would be good to leverage the existing tests to exercise the collation code.  Investigate
running all the tests against a collated database.
> Kathey

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

View raw message