[ 
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 that adds databaseProperties.sql to the list of scripts run 
in StoreScriptsTest. 
The teardown method now removes the system property set in 
databaseProperties.sql (derby.storage.pageSize), which was affecting the 
AccessTest. There was a method already present in BaseTestCase for this.
(the failing test fixture in AccessTest was: testLoadLongColumnsCreateIndex, 
and in some cases, a subsequent fixture did not have the expected error).

I also added 2 test cases to databaseProperties.sql, to confirm that setting 
the property to an invalid value does indeed revert back to the default. In one 
test case the invalid value is 'a', in the other, 'NULL'.

This patch makes a modified suites.All (with just the EncryptionSuite following 
StoreScriptsTest) pass.

I intend to commit this if the full suite passes.
                
> 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.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