yep, that''s the idea. Let''s recheck naming convention before changing the rakefile, however, need to make sure we don''t have any name space collisions with test:. Thought I recalled seing test_units rather than test:units when I looked at a rail''s task for comparison, but not sure about that. oh, and when we do this the tmp directory used by the test cases can get pulled under test, i.e., test/tmp, it doesn''t need (and probably shouldn''t) be at the root level. I can do this reorg, or let me know if you''d rather. Think I''d like to get it out of the way early on rather than deferring, just get it over with. ~ Deb _____ From: Jeff Barczewski [mailto:jeff.barczewski at gmail.com] Sent: Saturday, June 03, 2006 3:03 PM To: djlewis at acm.org Subject: Re: [Masterview-devel] test directory structure That sounds good. Maybe something like this for the rake task names (borrowing from rails) rake test # Test all units and functionals rake test:functionals # Run functional tests rake test:integration # Run integration tests rake test:units # Run unit tests As long as they all exist somewhere under the single main test directory I am ok with it (ie. subdirectories are fine). Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20060603/61237ec9/attachment.htm