[
https://issues.apache.org/jira/browse/DERBY-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houx Zhang updated DERBY-5342:
------------------------------
Attachment: 5342-6-testing.patch
In 5342-6-testing.patch, ij3Test sets "ij.showNoConnectionsAtStart" to false,
props.setProperty("ij.showNoConnectionsAtStart", "false");
but the test still passes, which is not expected. Furthermore,
utilMain.goScript() show the property is still true.
This is because ScriptTestcase.setUp() run after SystemPropertySetUp.setUp(),
so the two properties setted in SystemPropertySetUp.setUp() will be covered.
Now, let's return to 5342-3.patch, and to focus on why
LocalizedAttributeScriptTest and LocalizedDisplayScriptTest are affected by
ijConNameTest.
> 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
> Fix For: 10.9.0.0
>
> 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,
> 5342-6-testing.patch
>
>
> 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
