activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-5621) Unit tests cleanup
Date Tue, 10 May 2016 14:06:13 GMT

    [ https://issues.apache.org/jira/browse/AMQ-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278140#comment-15278140
] 

ASF subversion and git services commented on AMQ-5621:
------------------------------------------------------

Commit 3da9b0720efa4f8c55b8d04d3b584637a25ac1da in activemq's branch refs/heads/master from
[~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3da9b07 ]

https://issues.apache.org/jira/browse/AMQ-5621

Remove hard coded port as the bridge brokers method doesn't need the
port to be fixed.  Turn off JMX since the test doesn't use it.  

> Unit tests cleanup
> ------------------
>
>                 Key: AMQ-5621
>                 URL: https://issues.apache.org/jira/browse/AMQ-5621
>             Project: ActiveMQ
>          Issue Type: Improvement
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>
> Many of the existing test cases take longer than they should and fail randomly due to
BrokerService instances that are still running that have open JMX connectors etc.  We should
take some time to review tests and clean up were we can.  
> Removing hard sleeps and using admin view to check statistics can dramatically shorten
a test.  Also the tests can be configured not to create JMX connectors as none of them need
that in the normal case.  
> Other tasks that could be done is to update tests to JUnit 4 based tests with test timeouts
to help prevent CI hangs.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message