Commit Graph

12 Commits

Author SHA1 Message Date
Ryan Highley 6e4af114f1 NO-JIRA - Hacking Guide Branch Name Updates
Updates the hacking guide docs to correct the branch names as "main"
2023-02-03 10:40:48 -05:00
Robbie Gemmell 9873fccf74 ARTEMIS-4020: switch to using SLF4J API for logging, use Log4J 2 as impl for broker distribution and tests
PR includes work from myself and Clebert Suconic, squashed from the new-logging branch.
2022-09-28 14:01:54 -04:00
Domenico Francesco Bruscino b0f131f080 ARTEMIS-3694 Support remote servers for console smoke tests 2022-02-23 20:39:11 +01:00
nbrendah ff0e97150e Broken link in tests.md 2021-11-29 12:03:41 -05:00
Domenico Francesco Bruscino 5a5794021c ARTEMIS-3044 Add Artemis web console tests 2021-03-10 08:23:13 -05:00
Clebert Suconic 5e594cc18f ARTEMIS-2732 Updating hacking guide 2020-04-22 23:08:46 -04:00
Jiri Danek 472e429540 NO-JIRA fix warnings from w3c/link-checker in docs
also update URLs and `s/http/https` in docs wherever possible
2018-01-10 13:07:40 +01:00
Otavio R. Piske 5325c9db87 ARTEMIS-1291 - fix incorrect links in the documentation 2017-08-31 10:30:52 -04:00
jbertram 666b6ae03b Update hacking guide; add example tests 2015-05-28 12:20:35 -05:00
jbertram 328611fdc9 More test-suite refactoring
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
2015-05-28 08:49:02 -05:00
jbertram 99147d0713 Refactor base test classes
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.
2015-05-19 15:27:13 -05:00
jbertram 70258865a5 Initial commit of the hacking guide 2015-05-19 15:24:51 -05:00