To continue my series on Mocking Katas (see Mocking Kata – Instrument Processor for the last Kata), I’ll show you a very simple Kata that I normally use in my Test Driven Development training courses to introduce mocks (created manually or dynamically with the use of a mocking framework): the CharacterCopier.
This is the slide deck of a presentation I gave for bbv Software Services AG at two events in 2009 along with some comments .
If you are interested in seeing this presentation live (either in German or English) then please contact me.
In an agile project, the architecture has to evolve together with the requirements and the code. In this presentation, I’ll show you our agile architecture lifecycle.
We use Coding Katas in Coding Dojos to improve our programming skills. This includes skills in software design, refactoring, Test Driven Development, Mocking, tool usage and a lot of other tiny stuff.
However, I found only a few Katas, especially Katas including the need for mocks (see for example http://codingkata.org/). Most Katas are very algorithmic, which is good for learning TDD. But its bad for learning how to use mocks.
Therefore, I started to invent my own Mocking Katas. I use these in my training courses on Test Driven Development.
Living and breathing Scrum means for a team being self organized. My experience in different Scrum projects tells me that this is not always an easy task to grasp. Experienced Agile teams are self organized when it comes to maintain the code base or gathering information for user stories from the product owner. But what happens when soft skills are involved?
Once again, a new book joins the books I’ve read on my shelf: Agile Coaching by Rachel Davies and Liz Sedley.
Take a look at the books page for my short review.
Happy reading!
Test Driven Development (TDD) is often reduced to the three phases
There is nothing wrong about these three steps. But there is more involved in test-driving your development.