[
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_1.diff
DERBY-5977_1.stat
Attaching a patch that shows what .sql files I think can be run through the
junit scriptest mechanism and what changes need to be made to the .sql files
and masters to accomodate this.
This is a massive patch, because of white space diffs and other minor changes
in the .sql scripts and masters, but the more interesting change is the new
test StoreScriptsTest.java.
There is also a new StoreHarnessJavaTest.java, which maybe can run (some of)
the old java tests, but I've not worked on that one yet.
The main issue I have with the new StoreScriptsTest.java is that I could not
get the scripts to work correctly unless I modified every "connect 'wombat'"
statement to "connect 'jdbc:derby;wombat".
This however does force a call to DriverManager, making it impossible for these
tests to run under (current) J2ME platforms which only have DataSource
available.
I *thought* this would be unnecessary if I set the properties for ij.protocol,
but it didn't work.
Does anyone know how to address this?
> 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
>
>
> 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
