Test Cycle Length

Posted by Mike Haller on Wednesday, February 27. 2008 at 19:20 in Java
TddMeter gathers the average time it takes me to fix failed unit tests. I installed the plugin a few days ago. Currently, i'm working on a new project, mostly on documentation, prototyping and the core model - test driven of course :-)

I mention that, because working on an existing project or legacy code has a different amount of unit tests and the lifecycle is different. Working in the open countryside will have a faster test-cycle, while the documentation, analysis or prototyping phases are usually shaped by having no test cycles at all.

The TddMeter plugin shows the following stats for my last two days (since my last restart of Eclipse):
My TddPlugin stats of two days

The time between a test failure and the implementation of a fixture is approx. 22 minutes.
Don't know if this is a high or low value, but it sounds okay.

Let me know your stats!






Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications
 
Submitted comments will be subject to moderation before being displayed.
 

About

My name is Mike Haller and I'm a software developer and architect at Bosch Software Innovations in Germany. I love programming, playing games and reading books. I like good food, making photos and learning and mentoring about the craftsmanship of commercial software development. Stack Overflow profile for mhaller

Quicksearch