db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4709) Create test that parse client trace file to detect round-trips for Derby-4653
Date Wed, 23 Jun 2010 13:05:52 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kristian Waagan updated DERBY-4709:

    Attachment: derby-4709-1a-alternative_test.diff

Attached a proposal (1a) for the alternative test.

Patch ready for review.

BTW, now that the other test is in use, I don't think it it necessary to remove it  even if
this issue is completed. At least it would be good to keep both around for some time to make
sure the additional test is stable.

> 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:
>            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.

View raw message