Lots of work on the test-suite in this commit including:
- Rename ServiceTestBase to ActiveMQTestBase
- Make AddressSettings fluent
- Remove unnecessary tearDown() implementations
- Use ActiveMQTestBase.create*Locator() instead of
ActiveMQClient.createServerLocator*(..)
- Use fluent ServerLocator methods
- Make sure all ActiveMQServers.newActiveMQServer invocations
are surrounded with addServer() where appropriate
- Create a few example tests to be references from hacking-guide
- Update hacking-guide with more info on writing tests
- Refactor config creation methods in ActiveMQTestBase
DepAnn fail as ERROR for generated sources that implement deprecated methods,
but don't annotate with @Deprecated.
Also, see: http://errorprone.info/bugpattern/DepAnn
I have been playing with settings on the examples and the cluster settings are not really working by default
The default cluster-settings is using the wrong acceptor and the lack of max-hops is not making it work on most examples
maybe I will add some configuration on the max-hops through the create interface. I will set it as 0 for now at least
This has bothered me for awhile, but writing the hacking guide has
given me an opportunity to refactor some of our test-suite to be
simpler, more consistent, and easier to understand. This is
important if we want users to provide well-written tests. Our
test-suite is an important part of the code-base and it should be
easy to write good tests.
Basically I just consolidated CoreUnitTestCase, UnitTestCase, and
ServiceTestBase into a single class named ServiceTestBase. I also
simplified some of the configuration creation methods to reduce
duplicated code.
This is changing the default host to 0.0.0.0 per feedback from the community (activemq dev-list)
however if clustered is used some input or other properties will get input during the create process
I've also done some other changes based on some small issues I have encountered
Claus Ibsen
Clebert Suconic
jbertram
Thiago Kronig
Martyn Taylor
Andy Taylor