This week was very intensive in terms of education. First, a three-day training about Test-Driven Development at Pragmatists, then presentation about Vaadin by Bartek Kuczyński at Warsaw JUG meeting.
However, in this post I will focus on the most interesting thing, Test-Driven Development training and what I learnt there. The whole event lasted three days and in my opinion it was very effectively spent time. The only thing I didn’t like was a little too long theoretical introduction to the TDD and testing, but it is probably the feature of most trainings that the first chapter must be about only a theory. Fortunately, later it started to be much, much more interesting and the workshops began. They consisted of pair programming, writing tests, refactoring to patterns, mocking with Mockito, everything I expected from this training when I had enrolled. And everything in the amount that helped be to understand philosophy of software development with TDD on the practical side. Only a basic level, however, because to do it smoothly and quickly I have to spend a lot of time on Test-Driving and learning. But I did the first step.
Unfortunately at the beginning of this training it appeared that my lovely IDE (NetBeans) isn’t a natural-born IDE for TDD. And what’s the problem? NB isn’t smart enough when we are coding and trying to generate code by intention. For example, let’s compare process of creating testing method and how two IDEs: Eclipse and NetBeans are helping us in the following scenario: Continue reading this post …
Each one of us also have his beloved IDE. The most popular are NetBeans and Eclipse, both with many admirers and enemies who is always ready to argue that one IDE is great, and the other is passe. From time to time, unaware novice developer asks in one or another discussion group “Which IDE choose : Eclipse or NetBeans?” causing endless debate very similar to that in which some people try to prove the superiority of Christmas over Easter, while the other opts for the opposite proposition.