[
https://issues.apache.org/jira/browse/DERBY-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-1903:
--------------------------------------
Attachment: forced-order.diff
Although the purist in me prefers independent test cases, I think forcing a
particular order is OK to prevent the need for excessive setup code. The
attached patch forces the order of the test cases by using
TestConfiguration.orderedSuite(), which orders the test cases by their names.
The test cases happened to appear in alphabetical order in the source file, but
just to make it more obvious, I also added a serial number to the name of each
test case.
I didn't split up the existing test cases in smaller units, but that sounds
fine to me.
Committed revision 1149054.
> Convert largedata/LobLimits.java to junit
> ------------------------------------------
>
> Key: DERBY-1903
> URL: https://issues.apache.org/jira/browse/DERBY-1903
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: V.Narayanan
> Assignee: Kathey Marsden
> Priority: Minor
> Labels: LOB
> Attachments: DERBY-1903_liteToAllPackages_diff.txt,
> derby-1903_addsuites_diff.txt, derby-1903_client_diff.txt,
> derby-1903_embeddedp1_diff.txt, forced-order.diff
>
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
