I’ve been working hard the last six months teaching my teammates about unit testing, code reviews, SOLID, SCRUM and anything else I think we can benefit from. I feel lucky – for the most part they are open minded and accept my ideas and try them without prejudice, working this way has enabled better code … Continue reading Why you fail with TDD
Does this sounds familiar to you: You come to work early(ish) in the morning – ready to apply a new technology you’ve just learnt about – just to find out that you can’t. Your frustration grows as you understand that in order to use this “new and shiny” some adjustments must be made and what … Continue reading Using C# anonymous types to assert complex results in your unit tests
I was thinking about Reactive extensions (and using it) and then it hit me – why not try and use Reactive Extensions (Rx) in order to perform the FizzBuzz kata – it seems like a perfect fit.And so I set myself to try and use only Rx when performing this TDD kata. What is this … Continue reading FizzBuzz TDD kata– using Reactive Extensions
I’ve been having this problem ever since I’ve started teaching (and preaching) about SCRUM, clean code, unit testing and TDD and any other software development practice.When implementing a change – how do you measure its success?For that matter – how can you measure a developer productivity? by Our Hero A few years ago I … Continue reading Unit testing – you’re measuring it wrong
A while ago I was asked to talk about the problems of using TDD – being me I’ve decided to do the exact opposite, this session was names “what is wrong with TDD”.I felt that one of the major issues is that TDD looks weird, it’s counter-intuitive, and convincing developers to actually try it hard … Continue reading What’s wrong with TDD
Test Driven Development (TDD) have many benefits. For start it’s a design methodology that help avoiding “Analysis paralysis” and make sure that you only have the needed code to solve a problem.Yesterday I found another benefit of writing the tests before the code – you get to see them fail!A while back I wrote about … Continue reading Why you need to make your tests fail
A while back during a presentation on unit tests a member of the audience asked me a question I hope never to answer ever again – “So these unit tests you’re talking about, are they written by developers?” The reason I don’t particularly care for that question is that developers think that unit tests (and … Continue reading Why TDD is good for testers
Last week I conducted yet another code review. While looking at the code I’ve noticed a lot of lines similar to If(x != null) and if(y < 0) all over the code. These lines were not “business related” but were put in the code to make sure that proper inputs were given to the methods. … Continue reading Don’t fix invisible bugs
Unit testing your code is easy – all you need is to write simple test code and run it from time to time to check if your code misbehaves. But there is more to successfully using unit tests then just write these tests, in fact I saw quite a few talented developers get frustrated and … Continue reading Unit testing as a team sport
Helper Code 