Jakub is a Java EE developer since 2005 and occasionally a project manager, working currently with Iterate AS. He's highly interested in developer productivity (and tools like Maven and AOP/AspectJ), web frameworks, Java portals, testing and performance and works a lot with IBM technologies. A native to Czech Republic, he lives now in Oslo, Norway. Jakub is a DZone MVB and is not an employee of DZone and has posted 155 posts at DZone. You can read more from them at their website. View Full User Profile

Lesson Learned: Don't Use Low-Level Lib To Test High-Level Code

  • submit to reddit

Summary: Using a fake http library to test logic two levels above HTTP is unnecessarily complex and hard to understand. Fake instead the layer directly below the logic you want to test and verify the low-level HTTP interaction separately. In general: Create thin horizontal slices for unit testing, checking each slice separately with nicely focused and clear unit tests. Then create a coarse-grained vertical (integration-like) test to test across the slices.

The case: I want to test that the method login sends the right parameters and transforms the result as expected. Login invokes post-raw which calls an HTTP method. Originally I have tried to test it by using the library clj-http-fake but it proved to be unnecessarily complex. It would be much better to fake post-raw itself for testing loginand test the original post-raw and its HTTP interaction separately, using that library.

There are two problems with using the low-level clj-http-fake library for testing the login function:

  1. Both the calls I need to make need to be wrapped in its with-fake-routes, which makes the test more complex.
  2. More seriously, I need to drop down from the level of Clojure data structures to JSON encoded as a String. The transformations between the two would pollute the test and be meaningless from the point of view of what I want to test.

Solution: Run instead login with a fake version of post-raw and, if desirable, test post-raw with clj-http-fake separately.


// "Business" logic
function login(..)
   authorizationToken = post-raw(...)
   return (new function derived from post-raw with some parameters such as auth.token bound)
// Test
fake post-raw(request) to return "my-authorization-token"
var post-authenticated = login(..)
assert post-authenticated is function
fake post-raw(request) to return request
assert post-authenticated(dummy-values) = {dummy-values + the auth. params}
// Testing post-raw isn't important now

See the clj-zabbix-api‘s core_test.clj for the full Clojure test and core.clj for the code. Disclaimer: It is not very good Clojure code. I am just learning :-)

Published at DZone with permission of Jakub Holý, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)