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

Myrna van Lunteren updated DERBY-5977:
--------------------------------------

    Attachment: DERBY-5977_3.diff
                DERBY-5977_3.stat

Attaching a patch which moves two .sql scripts from the storetests directory 
and suite to the StoreScriptsTest, and removes 1 .sql file altogether.

The storetests are merely a group of store tests that could run after one 
another while using the same database, there is functionality that sets them 
apart from other store tests, so there should be no objection to moving them 
over.

st_1.sql was the initial test created to ensure calls to the SYSCS_UTIL schema 
and its procedures can be made, but all the functionality is by now also 
covered in other tests, so I think it can just be removed.

If removing st_1.sql is not OK, I can move st_1 to the store directory 
instead...
                
> Run storemore and possibly other store .sql tests in junit harness using 
> ScriptTest mechanism.
> ----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5977
>                 URL: https://issues.apache.org/jira/browse/DERBY-5977
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>         Attachments: DERBY-5977_1.diff, DERBY-5977_1.stat, DERBY-5977_2.diff, 
> DERBY-5977_2.stat, DERBY-5977_3.diff, DERBY-5977_3.diff, DERBY-5977_3.stat, 
> DERBY-5977_3.stat
>
>
> There are a number of .sql tests in the storemore suite, which might be able 
> to in the junit framework through a scriptTest. 
> They can still be fully converted at a later stage if we need more control.
>  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to