[
https://issues.apache.org/jira/browse/DERBY-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-3696:
-----------------------------------
Attachment: derby-3696-1a-delete_longStringColumn_test.stat
derby-3696-1a-delete_longStringColumn_test.diff
'derby-3696-1a-delete_longStringColumn_test.stat' deletes the test, the master
output file and removes the test from the suite of old tests being run in the
new framework. suites.All and derbyall ran without failures.
An example of a similar test can be found in jdbcapi.BlobClob4BlobTest.
> Delete superfluous test lang/longStringColumn.java
> --------------------------------------------------
>
> Key: DERBY-3696
> URL: https://issues.apache.org/jira/browse/DERBY-3696
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.5.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Trivial
> Attachments: derby-3696-1a-delete_longStringColumn_test.diff,
> derby-3696-1a-delete_longStringColumn_test.stat
>
>
> The test "lang/longStringColumn.java" simply inserts a 65K characters long
> Java string into a Clob column and then retrieves it and compares it to the
> input.
> I planned to convert it, but since our existing JUnit tests already cover
> this functionality, I propose to delete the old style test.
> I'll wait a few days for feedback.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
