[
https://issues.apache.org/jira/browse/DERBY-5084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Houx Zhang updated DERBY-5084:
------------------------------
Attachment: derby-5084-7.patch
Thanks, Bryan and Myrna. I have summitted the new patch by your advice.
@Myrna
I have only run the tools.Suite, but not suites.All. And now, I have run the
complete test, and I'm sure the new patch doesn't make bad effect on old
testing.
Besides, I'm not sure whether it's neccesary to run the complete for this
patch, as it's just to have added a new test class, not changed any product
code, maybe it's safe even not run the complete test suite. It have cost me
over 5 hour in my PC for one run and I have to run again when testing was
broken down by accident.
> 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, derby-5084-6.patch, derby-5084-7.patch, 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
