X-FeedAbuse: http://nntpfeed.proxad.net/abuse.pl feeded by 88.191.16.109 Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!nospam.fr.eu.org!talisker.lacave.net!lacave.net!not-for-mail From: Suraj Kurapati Newsgroups: comp.lang.ruby Subject: [ANN] test-loop 11.0.0 Date: Thu, 14 Apr 2011 17:45:32 -0500 Organization: Service de news de lacave.net Lines: 44 Message-ID: NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1302821178 99550 65.111.164.187 (14 Apr 2011 22:46:18 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Thu, 14 Apr 2011 22:46:18 +0000 (UTC) X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 381574 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:2888 test-loop - Continuous testing for Ruby with fork/eval https://github.com/sunaku/test-loop#readme What is it? ----------- test-loop is a fast continuous testing tool for Ruby that automatically detects and tests changes in your application in an efficient manner: 1. Absorbs the test execution overhead into the main Ruby process. 2. Forks to run your test files without overhead and in parallel. 3. Avoids running unchanged test blocks inside changed test files. What is new? ------------ Incompatible changes: * The `test/loop/rails` preset has been internalized and is now applied automatically if your test execution overhead includes Ruby on Rails. New features: * If you are using Rails 3, test-loop will automatically set `config.cache_classes = false` for your test environment. (Brian D. Burns) Bug fixes: * Avoid deadlock errors when printing output from Test::Unit and MiniTest. (Brian D. Burns) `write': deadlock detected (fatal) * Signaled worker termination is neither pass nor fail. Do not treat it as a failure by printing the log file. * Ignore SIGINT in workers; only master must honor it. -- Posted via http://www.ruby-forum.com/.