[
https://issues.apache.org/jira/browse/DERBY-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471070
]
Daniel John Debrunner commented on DERBY-2304:
----------------------------------------------
I think this test shows a useful common pattern:
some SQL schema setup run once for a set of fixtures
(CleanDatabaseTestSetup.decorateSQL)
emptying the tables for each fixture (the setUp method)
Myrna's batchUpdate() test in DERBY-2293 I think shows the same requirement.
ProcedureTest has the same pattern.
Having a utility method to perform the emptying (all the DELETE FROM TABLE
commands) without having to explicitly list the tables in the test would be
useful. Currently we have tests implementing their own mechanisms and I think
the ProcedureTest approach is somewhat awkward in having to specify the table
name twice in the list.
Something like
JDBC.emptyAllTables(Connection conn)
it could pull logic from the code that drops all tables.
> Convert derbynet/callable.java to junit
> ---------------------------------------
>
> Key: DERBY-2304
> URL: https://issues.apache.org/jira/browse/DERBY-2304
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Jean T. Anderson
> Assigned To: Jean T. Anderson
> Priority: Minor
> Attachments: derby-2304-preview.diff
>
>
> Convert the derbynet.callable.java test to the junit framework.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
