So you have just developed this new feature and your application can calculate things. Some very, very important things. Business people are happy. ...at least for few days. Then they start asking questions. They want to know how the numbers you give were calculated.
Soft assertions - are they really so cool as they seem?
This is a short story of a bad "refactor" of test code. In Poland we say, that "dobrymi chęciami piekło brukowano", which basically means, that trying to do something good can lead to really bad results. Well, I tried to do something good and I failed. Let us take a closer look.
Recently during the lunch at work, we have discussed the operating systems. You know, the usual Windows vs. Linux vs. Mac stuff. The discussion wasn't very interesting, because no one opted for Windows. :) So, lacking an opponent, we moved to some Linux related issues.
Ok, so this is a rant. You won't learn anything about Java 8 Streams here. Sorry. This blog post is meant to express my frustration. It's flowing from my mind via keyboard to this blog post. I can't stop it. Sorry!
Some time ago I have decided to stop using services offered by Google. This is not because I'm disappointed with their quality or features!. It is because the latest Snowden/PRISM/NSA revelations and also due to the feeling that big companies (not only Google) are misusing my private data.
When discussing unit tests it often happen that I hear that "unit testing is about testing methods". I do not agree, and because this is something which surfaces here and there so I think the idea deserves a comment.
1000 words about Java generics.
There are some things which are not worth unit-testing. Really, there are. Getters/setters and delegators are the best examples.