RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  
 

Lemon Unit Testing Framework

Posted by trans on January 04, 2010 — 2 comments
I just released v0.6 of Lemon, a unit testing framework that enforces a one-to-one correspondence between test cases/units and classes/methods. While still an early development release, it's quite usable. And I'm curious to find out what others think of the approach.

Comments

“” the 1:1 ratio is only a very small component of good test coverage. how you write your tests is far, far more important. i'm sure i would find the constraint annoying and unnecessary at times, too. either you practice test driven development or you don't. if you don't, you won't use the framework. if you do, it probably won't help.kenny - January 04, 2010 04:31
“” Thanks for the feed back, it gives me some guide to addressing some potential misconceptions.

I grant you that how you write your tests is more important. But I think your conclusion is too strict. You've either have written a test or you haven't. How it ultimately got there doesn't really matter once it is --test-driven or not. Tests are valuable even if they did not come first. TDD is a great thing, I am all for it. But it's certainly not as simple as "you practice test driven development or you don't" Moreover, one can do test driven development at a functional level, and then subsequently improve test coverage later with lower-level unit tests.

But all that aside, the 1:1 ratio provides a guide --to focus unit test concerns on the unit level.trans - January 04, 2010 07:25
“”

Post a Comment

Comment abilities for non registered users are currently deactivated, pending time to add a proper CAPTCHA to solve the escalating spam problem. Sorry!