[
https://issues.apache.org/jira/browse/DERBY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12882505#action_12882505
]
Kristian Waagan commented on DERBY-4709:
----------------------------------------
Hi Lily,
I'm sorry, I do not understand what you mean regarding a more accurate
verification.
With the exception of the extra commits, the exact same test sequence is run
twice on a fresh connection. The test criteria may be expressed like:
[common_work] = [common_work] + [unnecessary_commit_work]
What number do you want to know the value of?
Regarding the failure you are seeing, can you post the stack trace?
Is the test itself failing, or is SupportFilesSetup.tearDown failing?
> Create test that parse client trace file to detect round-trips for Derby-4653
> -----------------------------------------------------------------------------
>
> Key: DERBY-4709
> URL: https://issues.apache.org/jira/browse/DERBY-4709
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.7.0.0
> Reporter: Lily Wei
> Priority: Minor
> Attachments: derby-4709-1a-alternative_test.diff
>
>
> In DERBY-4653, Kristian suggested we have a test that parse the trace file to
> detect round-trip Connection.flowcommit() instead of calling
> getClientTransactionID() method. The existing test for DERBY-4653 is in
> J2EEDataSourceTest.testConnectionFlowCommit(). When this issue get fixed, the
> call for getClientTransactionID can be replace with trace file parsing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
