Recently we got a great news.
They released Mockito 2.1.0 - after so many years of hopeless waiting!
There is a lot of cool updates in Mockito 2, including:
Yes! I must use it! - I decided.
What a huge disappointment it was for me…
Six years ago I developed an enterprise project with Spring framework.
We believed that Spring is a bloody enterprise.
We wanted to get rid of this boilerplate.
We were young and courage, we wanted changes.
My interview for jug.ru About Legacy code without maximalism.
Including: TDD, sport, Sherlock Holmes and real men.
Typically you need to create a lot of various objects with various states in your tests. But you don’t always have appropriate constructors, and probably don’t want to have too many constructors.
And Java 8 can help here!
Christmas is a time for miracles. On the eve of the new year we all build plans for the next. And we hope that all problems will leave in the ending year, and a miracle happens in the coming year.
Every Java developer dreams about a miracle that lets him become The Most Effective Java Developer in the world.
I want to show you such a miracle.
It’s called automated tests!
There are “eternal” questions that have no single correct answer. E.g. what is better: Windows or Linux, Java or C#; who is stronger, Chuck Norris or Van Damme. One of such holywars is selection of the best Java IDE.
I have heard many times the term “logic” or “business-logic” in discussions about software development. For instance:
Now tell me, what is “logic”?
not translated yet
TDD is not absolute goodness. Tests can be different.
Let’s consider how bad can be unit-test and how can it evolve.
It is believed that a good program should be well documented.
SUN company even creared a special format javadoc - “a standard for documenting classes Java”. In fact, it was quite a common case in my experience, when a code did not pass Code Review just because some of its methods lacked comments.
Today I’ll tell you why the comments are evil.