You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Matt Lovett (JIRA)" <ji...@apache.org> on 2006/12/06 11:01:22 UTC
[jira] Resolved: (SANDESHA2-54) Tests are slow, and have fragile
timeouts
[ http://issues.apache.org/jira/browse/SANDESHA2-54?page=all ]
Matt Lovett resolved SANDESHA2-54.
----------------------------------
Resolution: Fixed
> Tests are slow, and have fragile timeouts
> -----------------------------------------
>
> Key: SANDESHA2-54
> URL: http://issues.apache.org/jira/browse/SANDESHA2-54
> Project: Apache Sandesha2
> Issue Type: Improvement
> Reporter: Matt Lovett
> Assigned To: Matt Lovett
> Priority: Minor
> Attachments: tests.patch
>
>
> The unit tests often use Thread.sleep to wait for the async message exchanges to complete. The timeout of the sleep varies from place to place, and occasionally needs to change. I would like to refactor the code so that there is a consistent limit, and the tests check at more frequent intervals to see if the message exchange has completed. This should speed up the time it takes to run the tests, as well as making them more resilient to changes in the implementation.
> I'll also refactor common test code up to SandeshaTestCase, and remove references to some deprecated code for each file I need to touch.
> Patch to follow...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org