[
https://issues.apache.org/jira/browse/DERBY-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12465643
]
Daniel John Debrunner commented on DERBY-2095:
----------------------------------------------
Also the Populate class contains the same checks as LoadTester. On of the nice
things about Junit test fixtures is that it's easy to hook them together. One
can see test fixtures as building blocks.
So if Populate needs to run the tests it could just include checks indvidually,
like:
suite.addTest(new OETest("testOrdersRows"));
or through some suite like:
suite.addTest(OETest.checkAllRowCounts());
Though I think it would be better to have the checks be in a separate class,
e.g. Checks, and have OETest and Populate include fixtures from Checks.
> Add the ability to populate a database for the order entry toolkit based upon
> the TPC-C specification.
> ------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2095
> URL: https://issues.apache.org/jira/browse/DERBY-2095
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Reporter: Daniel John Debrunner
> Assigned To: Sunitha Kambhampati
> Priority: Minor
> Attachments: oe.load.p1.diff.txt
>
>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
