[
https://issues.apache.org/jira/browse/DERBY-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houx Zhang updated DERBY-5342:
------------------------------
Attachment: 5342-5.stat
5342-5.patch
Yes, Bryan. I agree that it's better to add the properties setting into the
constructor of ScriptTestCase. It works well just like in 5342-5.patch. Please
check it.
As to why IjConnNameTest affected other tests, I think it has been resolved in
the new patch.
> make ScriptTestCase support "ij.showNoCountForSelect" and
> "ij.showNoConnectionsAtStart"
> ---------------------------------------------------------------------------------------
>
> Key: DERBY-5342
> URL: https://issues.apache.org/jira/browse/DERBY-5342
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Houx Zhang
> Assignee: Houx Zhang
> Labels: gsoc2011
> Attachments: 5342-1.patch, 5342-2.patch, 5342-2.stat, 5342-3.patch,
> 5342-3.stat, 5342-4-test.patch, 5342-5.patch, 5342-5.stat
>
>
> Now, ScriptTestCase doesn't support property "ij.showNoConnectionsAtStart"
> (do nothing for it) and "ij.showNoCountForSelect"(it always works as
> "ij.showNoCountForSelect" = "flase").
> It will be better if the two properties be supported. To realise this,
> utilMain.goScript(Connection conn, LocalizedInput in) should be changed.
> Besides, some subclasses of ScripTestCase will be adapted accordingly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
