[ANN] test-loop 12.0.0

Discussion in 'Ruby' started by Suraj Kurapati, Apr 20, 2011.

  1. 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:

    * You must now explicitly `require 'test/loop/rails'` for Rails
    support because we can only *automatically* apply our Railtie (to
    disable class caching) after the overhead has been loaded, and by
    then it's too late: your models are already loaded & cached by the
    Rails environment.

    * Your tests can no longer read from the user's terminal (master's
    STDIN); instead they will read from an empty stream (the reading
    end of IO.popen).

    Bug fixes:

    * Replace threads with SIGCHLD for reporting test results.

    This fixes deadlock errors that sometimes occurred when the user's
    chosen test library tried to print something to STDOUT/STDERR
    (even though those streams were redirected to a log file in the
    worker process).

    Thanks to Brian D. Burns for suggesting and verifying that the use
    of threads to monitor workers was the culprit behind the deadlocks
    errors.

    * Ctrl-C did not raise Interrupt in my Rails 3 test suite.

    Housekeeping:

    * Ensure a clean ENV when reabsorbing overhead. Environment
    variables set by your test execution overhead are not propagated
    to subsequent reabsorptions. (Brian D. Burns)

    * Call `setsid()` to detach worker from master's terminal.
    <http://stackoverflow.com/questions/1740308#1740314>

    * Mutex is not needed since we only use GIL'ed array methods.
    <http://www.ruby-forum.com/topic/174086#762788>

    * Remove redundant STDOUT coercion after loading user's testing
    library.

    * Further simplify `Test::Loop.run()` by higher-order programming.

    Documentation:

    * Add prerequisites section about POSIX environment.

    * Add tip about annihilating test-loop processes.

    * Fix markdown formatting.

    --
    Posted via http://www.ruby-forum.com/.
    Suraj Kurapati, Apr 20, 2011
    #1
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Skybuck Flying

    Call oddities: &Test() vs &Test vs Test

    Skybuck Flying, Oct 4, 2009, in forum: C Programming
    Replies:
    1
    Views:
    694
    Skybuck Flying
    Oct 4, 2009
  2. Suraj Kurapati
    Replies:
    7
    Views:
    107
    Suraj Kurapati
    Jan 14, 2011
  3. Suraj Kurapati

    [ANN] test-loop 5.0.0

    Suraj Kurapati, Jan 17, 2011, in forum: Ruby
    Replies:
    0
    Views:
    102
    Suraj Kurapati
    Jan 17, 2011
  4. Suraj Kurapati

    [ANN] test-loop 5.0.3

    Suraj Kurapati, Jan 25, 2011, in forum: Ruby
    Replies:
    0
    Views:
    96
    Suraj Kurapati
    Jan 25, 2011
  5. Isaac Won
    Replies:
    9
    Views:
    372
    Ulrich Eckhardt
    Mar 4, 2013
Loading...

Share This Page