river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Costers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-301) Move the QA framework donated by Sun inside the jtsk trunk and integrate into build process
Date Sat, 18 Sep 2010 19:03:33 GMT

    [ https://issues.apache.org/jira/browse/RIVER-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911068#action_12911068

Jonathan Costers commented on RIVER-301:

-> fails consistently for me when the QA harness is run in transient mode, but passes when
the harness runs in activatable mode. Maybe needs to be configured to be skipped in transient

-> failed for me but the reason was because the test code was trying to catch a different
kind of Exception (UnknownTransactionException), where logically a CannotCommitException would
be expected. Changing to CannotCommitException passes the test.

-> this test seems to hang, at the end of the test code it is stuck in a while loop waiting
for a TransactionException to be thrown ...

The rest of the tests in the txnmanager category all pass.

It would be good if the original author would be able to comment, but not sure if that is

> Move the QA framework donated by Sun inside the jtsk trunk and integrate into build process
> -------------------------------------------------------------------------------------------
>                 Key: RIVER-301
>                 URL: https://issues.apache.org/jira/browse/RIVER-301
>             Project: River
>          Issue Type: Task
>          Components: other
>    Affects Versions: AR3
>            Reporter: Tom Hobbs
>            Assignee: Jonathan Costers
>         Attachments: integrationtest.xml, RIVER-301-JC-5.1.patch, RIVER-301-JC-6.0.patch.tar.gz,
RIVER-301.patch, RIVER-301.patch, River-301.patch.zip, River-build-qa5.patch
>   Original Estimate: 672h
>  Remaining Estimate: 672h
> The tests donated by SUN live in their own source project and are runnable in a format
that is unfriendly towards IDEs and new developers to the River project.
> This is the proposal to move the test code, mostly unmodified, into the main source directory
whilst shoe-horning it into JUnit 3.  This will allow it to be easily viewable and runnable.
 Such a structure will also reduce the code-compile-test cycle since no JARs will have to
be created in the middle of the cycle and no long command-line incantations.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message