Fortsätt till huvudinnehåll

Professional Test-Driven Development with C# - Review of the first 5 chapters

There is a lot of resources available online when it comes to TDD. However, I have always found that a good book is better than most online resources. Therefore I borrowed home a book called 'Professional Test-Driven Development with C#' by James Bender and Jeff McWherter.

So far I am 5 chapters in to the book (about 1/3) and here is some of my reflections regarding the content:
  • The book provides many code examples, which is positive. There is however at least one code listing that is incorrect (looks like the wrong listing was inserted).
  • The authors put great emphasis on Red-Green-Refactor. That no application code should be written before there is a failing test for it. Still in chapter 5 they write the application code first and then add the tests later - WRONG!
  • A lot of focus is put on the use of frameworks. I understand that you shouldn't re-invent the wheel and that choosing a good test framework, like NUnit, is a good thing to do. However, you should be careful not to make your application too dependent on external frameworks that you do not have any control over. Examples of frameworks that are mentioned are NUnit, Moq, Ninject, Entitiy Framework, and NHibernate.
  • Principles like SOLID are mentioned and described briefly. If you are totally unfamiliar with SOLID I recommend reading up on those before diving into this book. The explanations are good for refreshing existing knowledge on SOLID but not enough if you don't have any previous experience of it.
Despite the short-comings mentioned above, so far I find the book to be a good read. It will be interesting to see what the next 2/3 will be like.

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i...
7 kommentarer
Läs mer

Does TDD really improve software quality?

I have asked myself this question several times, and searched for answers, without coming up with any clear answer. Therefore I have decided to go hard core TDD for a longer period of time (at least 6 months) to really evaluate the effects. There are several things that I find confusing when it comes to TDD. One example is what actually defines a unit test. What is a "unit" anyway? After reading a bit about it I found a text claiming that the "unit" is "a unit of work", i.e. something quite small. Like converting a string to UPPERCASE or splitting a string into an ['a','r', 'r', 'a', 'y'] of chars. This work is usually performed by a single call to a single method in a single, isolated, class. So, what does it mean that a class is isolated? Does it mean that it doesn't have any dependencies to other classes? NO! In the context of TDD it means that any dependencies are supplied by the test environment, for exa...
3 kommentarer
Läs mer

Is it necessary to have some basic knowledge of algorithms and datastructures in order to be a good programmer?

The short answer, yes, absolutely. This is a follow up to my previous blog post where I claimed that you don't need to know advanced algorithms by heart in order to be a good programmer. That is still totally true. However, you should have at least some basic understanding of algorithms and data structures. Having this knowledge will help you select the correct tools for the job, for example knowing when to use a stack over a queue, when a linked list is a better selection than an array, when to use a hashset, or a dictionary, and so on. This will help you write easier and more robust code. It is also a really good idea to have some feeling for how your code will perform when input data grows. How will memory consumption and running time be effected if the input data grows by a factor 100, or 1000? This knowledge will help you identify performance bottlenecks in your application and help you come up with ideas on how to attack them. So, if you haven't done it already, ta...
3 kommentarer
Läs mer