Just a positive experience I would like to share with you : testing is great on paper but very tedious to apply because nobody wants to run manually the tests by hand. Last week I have discovered zentest, an automated test process command line utility. That was at the beginning (hopefully) of a new project. Believe it or not, I have started to code most parts of the application without using a web browser for the first time of my life !! Now, I have reached 51 tests and 140 assertions and everything is smoother and smoother - The fear is gone ! Usage is as simple as : autotest -rails from the root of your app, then write your tests. Be nice with yourself, use zentest : http://www.zenspider.com/ZSS/Products/ZenTest/ And a big thank to the author : Ryan Davis - Can the zen be over his head for the rest of his life :-)) -- Posted via http://www.ruby-forum.com/.
nuno wrote:> Just a positive experience I would like to share with you : testing is > great on paper but very tedious to apply because nobody wants to run > manually the tests by hand. > Last week I have discovered zentest, an automated test process command > line utility. That was at the beginning (hopefully) of a new project. > > Believe it or not, I have started to code most parts of the application > without using a web browser for the first time of my life !! > > Now, I have reached 51 tests and 140 assertions and everything is > smoother and smoother - The fear is gone ! > > Usage is as simple as : > autotest -rails from the root of your app, then write your tests. > > Be nice with yourself, use zentest : > http://www.zenspider.com/ZSS/Products/ZenTest/ > > And a big thank to the author : Ryan Davis - Can the zen be over his > head for the rest of his life :-)) > > > >+1
> Be nice with yourself, use zentest : > http://www.zenspider.com/ZSS/Products/ZenTest/I agree with you, autotest(part of zentest gem) is very cool tool. I discover it a few month ago and now I always use it. It tell me if all was good and if any of my change break no other part of my application. All that thing without additional work, it run on the background and see if I make no errors in my code. If your on mac os X, you can be alert by growl if test break. It require an aditional gem and a rails plugin but iI think it can be interssant. Do you try other programs in the zentest package, particulary zentest himself ? I plan to use it but i don''t know if it generate test for rails app. -- Posted via http://www.ruby-forum.com/.
nuno wrote:> Usage is as simple as : > autotest -rails from the root of your app, then write your tests.It looks like a great tool; pity that I can''t seem to find any documentation for it. Any other tips on how to use it? d -- Posted via http://www.ruby-forum.com/.
Dewet Diener wrote:> nuno wrote: >> Usage is as simple as : >> autotest -rails from the root of your app, then write your tests. > > It looks like a great tool; pity that I can''t seem to find any > documentation for it. Any other tips on how to use it? > > dYes there is not a lot of docs but the most important part of zentest is usable without any manual : i''m talking about autotest. 1) gem install 2) in your rails root type "autotest -rails" You''re done ! Guillaume : no I only used autotest - may be I should have a look but I don''t like generators too much -- Posted via http://www.ruby-forum.com/.
nuno wrote:> Dewet Diener wrote: >> nuno wrote: >>> Usage is as simple as : >>> autotest -rails from the root of your app, then write your tests.But there aren''t even enough docs to tell you what will happen if you "autotest -rails". What does it do? When does it do it? How will I know what happened? <soapbox> If you ask me, documentation, or a lack of it, is the achilles heal of Rails (and Ruby). A list of methods is not documentation. RDoc is the worst idea in Ruby, and sadly, the great group of folks who put together rails just went with the flow. Really sad. Good people who put together supposedly useful tools like ZenTest also seem to just go with the flow. Even more sad.</soapbox> jp -- Posted via http://www.ruby-forum.com/.
nuno wrote:> Usage is as simple as : > autotest -rails from the root of your app, then write your tests. > > Be nice with yourself, use zentest : > http://www.zenspider.com/ZSS/Products/ZenTest/I would also recommend you additionally install Cerberus build tool. http://rubyforge.org/projects/cerberus Unlike ZenTest (that runs tests only for you) Cerberus would run automatically tests if any of your team do commit to repository. In nearest few days it would be available 0.2.0 release that brings new publishers: Jabber, IRC, RSS (in addition to existed mail publisher) + new builder for Maven2. So it would be possible to use Cerberus for Maven2 projects as lightweight alternative to CruiseControl and Continuum. -- Posted via http://www.ruby-forum.com/.
This topfunky entry may help a bit(screencast) http://nubyonrails.com/articles/2006/04/19/autotest-rails plus this will help out with getting tests to broadcast to growl: http://thatswhatimtalkingabout.org/news/2006/6/8/make-your-tests- roar#ajax-update J On 11-Aug-06, at 8:03 AM, nuno wrote:> Dewet Diener wrote: >> nuno wrote: >>> Usage is as simple as : >>> autotest -rails from the root of your app, then write your tests. >> >> It looks like a great tool; pity that I can''t seem to find any >> documentation for it. Any other tips on how to use it? >> >> d > > Yes there is not a lot of docs but the most important part of > zentest is > usable without any manual : i''m talking about autotest. > > 1) gem install > 2) in your rails root type "autotest -rails" > > You''re done ! > > Guillaume : no I only used autotest - may be I should have a look > but I > don''t like generators too much > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails
[this post was lost, so I''m sending again - mailman pooching?] This topfunky entry may help a bit(screencast) http://nubyonrails.com/articles/2006/04/19/autotest-rails plus this will help out with getting tests to broadcast to growl: http://thatswhatimtalkingabout.org/news/2006/6/8/make-your-tests- roar#ajax-update J On 11-Aug-06, at 8:03 AM, nuno wrote:> Dewet Diener wrote: >> nuno wrote: >>> Usage is as simple as : >>> autotest -rails from the root of your app, then write your tests. >> >> It looks like a great tool; pity that I can''t seem to find any >> documentation for it. Any other tips on how to use it? >> >> d > > Yes there is not a lot of docs but the most important part of > zentest is > usable without any manual : i''m talking about autotest. > > 1) gem install > 2) in your rails root type "autotest -rails" > > You''re done ! > > Guillaume : no I only used autotest - may be I should have a look > but I > don''t like generators too much > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails
Please Do Investigate On 8/11/06, Jeff Pritchard <jp@jeffpritchard.com> wrote:> > nuno wrote: > > Dewet Diener wrote: > >> nuno wrote: > >>> Usage is as simple as : > >>> autotest -rails from the root of your app, then write your tests. > > But there aren''t even enough docs to tell you what will happen if you > "autotest -rails". What does it do? When does it do it? How will I > know what happened? > > <soapbox> > If you ask me, documentation, or a lack of it, is the achilles heal of > Rails (and Ruby). A list of methods is not documentation. RDoc is the > worst idea in Ruby, and sadly, the great group of folks who put together > rails just went with the flow. Really sad. Good people who put > together supposedly useful tools like ZenTest also seem to just go with > the flow. Even more sad.</soapbox> > > jp > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060814/3fccc366/attachment.html