|«« Abstractulate Yourself||A Server for Every Occasion »»|
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005
» Former committer for RadRails (now Aptana)
» I also have a few Rails side-projects in development:
1. wheretogoinTO.com Toronto nightlife
2. Hey Heads Up! TODO list and sharing
3. Layered Genealogy family history research
4. foos for foosball scoring
5. fanconcert for music fans (on hold)
Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada
»» Email: rails AT ryanlowe DOT ca
Now hosted on Hey! Heads Up -- check it out!
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
email@example.com no more
Forging Email Headers: Good, Bad or Ugly?
Sarcastic Dictionary (Part 1 of Many)
Twisting Rails is Risky Business
Risky Business? My Take on Early Alphas
Whoa, it's August 2007
A Postscript to "Growth at the grassroots"
»» All Blog Posts
David Heinemeier Hansson
James Duncan Davidson
Signal vs. Noise
Amy Hoy: (24)slash7
Luis de la Rosa
My xUnit Wishlist
1. Automatic unit tests.
For example, if one or more (in) parameters passed to a function is null, what does the function do? This check should be automatic in unit testing and should not have to be written explicitly save for the result. If a test isn't written at all, the unit tester should complain.
2. Tests for specific defects.
A defect is opened. To close it, you need to write a test that replicates the defect and make sure it fails with the current code. Then you change (refactor/repair) the program code until it passes. Now you have a regression test for this defect and if the test fails you know the defect is back.
3. Built-in code coverage analysis
If you are truly doing test-driven development, at any given time all lines in the program code should be executed by all tests. If this is not true, develop tests to exercise these lines or, even better, get rid of the superfluous lines.
4. A user-interface library that supports verification.
How can I be sure that the user interface is correct at any given time without manually verifying it? The UI library should be written so that any element in the UI can be programmatically checked for properties such as visibility, position, etc. To see how involved this task can be, check out Liar Views.
5. User-interface can be controlled programmatically
Any defect replicated in the field must be able to be replicated programmatically for a unit test.Posted at November 16, 2002 at 12:26 AM EST
Last updated November 16, 2002 at 12:26 AM EST