db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-4047) tests updatelocks and updatelocksJDBC30.sql are not run anywhere; should get evaluated
Date Tue, 09 Jun 2009 18:26:07 GMT

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

Mike Matrigali resolved DERBY-4047.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.0.0

checked in new master and added to the store nightly suite.  Am resolving it, if someone wants
to convert this test open another issue.  Converting the test would not be too hard, just
need to be able to queries on the lock 
table.  It actually will be much cleaner as a converted test as it uses "sub" scripts which
really want to be program calls to a single routine after varying the setup.  The problem
is that calling the single routine 
returns different expected results based on the setup.  

> tests updatelocks and updatelocksJDBC30.sql are not run anywhere; should get evaluated
> --------------------------------------------------------------------------------------
>
>                 Key: DERBY-4047
>                 URL: https://issues.apache.org/jira/browse/DERBY-4047
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Assignee: Mike Matrigali
>            Priority: Trivial
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY-4047_a.diff
>
>
> I noticed the tests store/updatelocks.sql and store/updatelocksJDBC30.sql are not in
use.
> They should get evaluated for inclusion in the tests - they should either get included
- and preferably converted to junit - or get deleted.

-- 
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