Writing technical documentation is already a hard problem, and it gets harder when the tooling around it fights you every step of the way. This DenverJUG meetup opened with a look at AsciiDoc, a lightweight alternative to wrestling with XML-based documentation schemas or clunky WYSIWYG editors. The pitch is simple: write in a format that’s actually pleasant to work in, and still be able to produce clean HTML, PDF, and even slide decks from the same source.
The second half of the evening tackled a problem a lot of enterprise Java developers know all too well: the gap between unit tests and true integration tests. Unit tests and mocks only get a team so far. Eventually, you need to validate how your components behave in something closer to their real runtime environment, and that usually means taking on the burden of bootstrapping infrastructure just to run a test.
We looked at how a container-oriented testing framework can close that gap, bringing the test to the runtime instead of forcing the runtime to be assembled around the test. A companion tool handles packaging test archives with fine-grained control over which resources are available, and the combination lets developers write integration tests that feel almost as simple as unit tests, while staying portable across different environments and containers.
The bigger idea behind both halves of the night’s discussion was the same: enterprise Java tooling has a reputation for being heavyweight, but there’s real, ongoing work in the ecosystem to make both documentation and testing feel a lot less like a chore.
Thanks to everyone who joined the discussion, and to the sponsors who help keep DenverJUG meetups free and open to the Denver software community.