Hi all, I have a question regarding testing in ActiveMQ.
I’m noticing that many tests under activemq-unit-tests are very scoped to a single module, and (at least at first glance) could live alongside the code they test. On recent PRs, this pattern seems to continue. Is there a rule or guideline that unit tests should be placed under activemq-unit-tests/ rather than in the module they belong to? Having a dedicated module makes sense to me for integration-style tests (or anything that needs a wider broker setup / multiple modules). But for tests that only exercise code within a given module, I’m curious what the rationale is (history, dependency constraints, shared test utilities, etc.). It’s not a problem per se, but activemq-unit-tests has grown quite large and is difficult to run locally. Splitting truly module-local tests back into their owning modules could make local iteration easier. Thanks in advance for any context! -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com
