[
https://issues.apache.org/jira/browse/ARTEMIS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15511334#comment-15511334
]
ASF GitHub Bot commented on ARTEMIS-737:
----------------------------------------
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/789
I think it would also be good to have a clear explanation of why this
approach is superior to the approach already adopted in the test-suite.
Additional questions:
1. What expectation is there to adopt this style of testing? Should all
new tests use this style?
2. Do you plan on converting all existing test-cases to this style? If
not, I'd be concerned with having 2 methods of doing the same thing introducing
confusion.
> Add JUnit Rules
> ---------------
>
> Key: ARTEMIS-737
> URL: https://issues.apache.org/jira/browse/ARTEMIS-737
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Quinn Stevenson
> Priority: Minor
>
> ActiveMQ includes a JUnit rule for embedding a JMS Broker. This would be a
> nice feature to have for Artemis as well, along with the JUnit rules for JMS
> Clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
