[
https://issues.apache.org/jira/browse/DERBY-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren updated DERBY-5084:
--------------------------------------
Attachment: DERBY-5084_5.diff
What Kathey said is true. I've modified the test once more, to eliminate the
noone protocol property; and adjusted the master/ijConnName.out file
accordingly.
If there are no comments I'll check that part of the converted test in.
I think the remaining property could get tested by making a separate test in a
similar way to the SysinfoCPCheckTest and SysinfoAPITest. There is no need for
a .sql script as there can be no connection; but if we catch the output in that
mechanism we can check for the string '08001' and 'Driver not found' in the
output.
> convert ijConnName.sql to a ScriptTest junit test
> -------------------------------------------------
>
> Key: DERBY-5084
> URL: https://issues.apache.org/jira/browse/DERBY-5084
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Myrna van Lunteren
> Assignee: Houx Zhang
> Priority: Trivial
> Labels: derby_triage10_8
> Attachments: DERBY-5084-1.patch, DERBY-5084-2.patch,
> DERBY-5084-3.patch, DERBY-5084-3.stat, DERBY-5084.patch, DERBY-5084_4.diff,
> DERBY-5084_5.diff, ijConnName-1.out, ijConnName-1.tmp
>
>
> In DERBY-3089 it is mentioned that tools/ijConnName.sql should get converted
> to a junit test, probably using ScriptTest.
> Making a separate issue so that that issue can be closed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
