[ http://issues.apache.org/jira/browse/DERBY-1371?page=all ]
Kathey Marsden updated DERBY-1371:
----------------------------------
Summary: Remove test harness special handling for handle varying client
column widths (was: Remove special handling for handle varying client column
widths)
> Remove test harness special handling for handle varying client column widths
> ------------------------------------------------------------------------------
>
> Key: DERBY-1371
> URL: http://issues.apache.org/jira/browse/DERBY-1371
> Project: Derby
> Type: Improvement
> Components: Test
> Versions: 10.1.2.4
> Reporter: Kathey Marsden
> Priority: Minor
>
> The test harness has code in FileCompare to normailze the column widths for
> test output to accommodate different column widths in embedded and client.
> I think the columnwidths should be the same so this is not needed for client.
> It would be good to remove this logic for client (but keep it for JCC) to
> make sure that client and embedded do indeed match in this regard. I think
> the harness change itself entails changing the section below in FileCompare
> to use isJCC Connection(framework) instead of isClientConnection: What
> differences will be found I don't know.
>
> if (NetServer.isClientConnection(framework))
> {
> try
> {
> Sed sed = new Sed();
> File JCCOutFile = new File(outDir, testBase +
> ".tmpmstr");
> sed.execJCC(is, JCCOutFile);
> is = new FileInputStream(JCCOutFile);
> }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
