[
https://issues.apache.org/jira/browse/DERBY-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481727
]
A B commented on DERBY-2399:
----------------------------
> Later the RunTimeStatistics class can be expanded to parse and return other
> information
> as needed for other tests. Does this strategy sound ok?
Sounds good to me. I was loosely considering doing something like this for a
new test that I'm writing for DERBY-47. In the end I just decided to do a
naive string search on the result set stats string to get what I need. But the
approach you mention here sounds better.
And when/if the work that Felix Beyer did is contributed, the RunTimeStatistics
class could be modified appropriately to take advantage of the new
functionality.
So yes, I like this idea :)
> Convert setTransactionIsolation.java to junit
> ---------------------------------------------
>
> Key: DERBY-2399
> URL: https://issues.apache.org/jira/browse/DERBY-2399
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
> Assigned To: Kathey Marsden
> Fix For: 10.3.0.0
>
> Attachments: derbynet.diff, derbynet.stat
>
>
> Convert setTransactionIsolation.java to junit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
