Being given so much unwanted opportunity of looking at bad, hurriedly written code recently, I can’t stop evangelising about unit tests. But don’t worry, today I’m going to write about something you problably haven’t seen yet. Behavior Driven Development. So, what’s wrong with TDD? Why do we bring another approach (assuming it’s not complementary - this is partially true). The problem with TDD (and writing unit tests in general) is that: to maintain them properly they need to be perfectly clear about what they do -> each test should represent a functional scenario…