# Searching on a suite of failing tests

Motivation Today, at a client, in the green phase, we had a test suite which was failing: the whole suite fails but the test cases, individually, succeed. So my first impression was that something was being shared between tests. Also confirmed because the failing class was an EndToEnd test, in which we load the whole spring context A quick glance was not revealing anything interesting, so I decided to find which is the minimum suite (as opposed as to the whole suite) that makes the new testcase fail, expecting to narrow the search for possible causes.

# Brown-bag session: Spring Boot

At a client, today we’ve done a brown-bag session on Spring Boot: we’ve gone through the basics with a sample maven project and its pom file. We’ve seen the Spring Initializr and a live demo, using curl for REST client.

# The Animal Laborans and the Homo Faber

I’ve found this quote very interesting from the book “The Craftsman”, by Richard Sennett: Animal laborans is, as the name implies, the human being akin to a beast of burden, a drudge condemned to routine. Arendt enriched this image by imagining him or her absorbed in a task that shuts out the world, a state well exemplified by Oppenheimer’s feeling that the atomic bomb was a “sweet” problem, or Eichmann’s obsession with making the gas chambers efficient.

# The language was prepared for that

Many times I’ve written this function: public boolean between(int lowerBound, int n, int upperBound){ return lowerBound <= n && n <= upperBound; } It may depend on the case, whether it is [], [), (] or (), to use mathematical terms. When the two comparisons are the same ([] and ()), there is duplication in the comparisons. Investigating a little bit on this in clojure, I’ve found this function: <= And its clojuredocs: Returns non-nil if nums are in monotonically non-decreasing order, otherwise false.