Ensuring JUnit test suite contains all tests

While cleaning up today one of my projects I found a JUnit test that was not part of a test suite and never was executed. 'Never again' I say and here is how: a test suite that scans base packages for tests. The particular code: Is tailored to the specific project's needs Compares the tests … Continue reading Ensuring JUnit test suite contains all tests →

A better eq() when matching method arguments with Mockito

I learned late of Mockito [1], even so more I love it. Walking a little farther away from the basics, a frequent needs presents itself to match method parameters (either when specifying or verifying behaviour) based on properties of complex objects which do not implement the java equals contract. Such an example would be verifying … Continue reading A better eq() when matching method arguments with Mockito →

Missing history update when clicking on links in GWT and HtmlUnit unittests

I'm still pretty enthusiastic about the benefits of templating [1] GWT UIs with HTML as it turns out to be a productive way for altering UIs without going through a tedious compilation and deployment procedure. HtmlUnit 2.9 is a great java browser for integration-testing Ajax applications. It works fine with GWT and we use it … Continue reading Missing history update when clicking on links in GWT and HtmlUnit unittests →

Spring @PathVariable mapping incomplete path when dots are included

In all my projects this happens at least once, and I'm surprised over and over again: a controller will not map just anything to @PathVariable by default. Contrary to intuition, the annotation's argument is a regular expression which excludes some characters per default. For instance the url http://localhost:8080/myapp/api/user/testuser@example when mapped to a controller: @RequestMapping(value = … Continue reading Spring @PathVariable mapping incomplete path when dots are included →

Cache collision and ehcache spring annotations module

If you are looking for a way to implement declarative caching with Spring, there is no way around Ehcache Spring Annotations [1]. This superimposes a transparent aspect on methods of any proxied bean, taking the method arguments as a key. Little known but easy to stumble upon [2] is an implementation (design?) quirk which expects … Continue reading Cache collision and ehcache spring annotations module →