ZenTest

Hi all,

I just discovered a nifty gem call ZenTest. I've just stated playing
around with the autotest command, which seem very cool and looks like
a nice time saver.

But, I did notice one very minor thing. When I use ^c to stop the
program I get the following error message:

^CInterrupt a second time to quit
^C/usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/autotest.rb:
131:in `initialize': wrong number of arguments (0 for 1)
(ArgumentError)
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:131:in `exception'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:131:in `raise'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:131:in `add_sigint_handler'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:274:in `call'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:274:in `sleep'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:274:in `wait_for_changes'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:101:in `get_to_green'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:84:in `run'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:82:in `loop'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:82:in `run'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:62:in `run'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/bin/
autotest:45
        from /usr/local/bin/autotest:16:in `load'
        from /usr/local/bin/autotest:16

Anyone know if this is a bug or am I exiting the program improperly?

Thanks once again to the great Ruby community for coming up with such
cool stuff.
Robert

So does anyone have any ideas about this?

Robert Walker wrote:

So does anyone have any ideas about this?

Hi all,

I just discovered a nifty gem call ZenTest. I've just stated playing
around with the autotest command, which seem very cool and looks like
a nice time saver.

But, I did notice one very minor thing. When I use ^c to stop the
program I get the following error message:

^CInterrupt a second time to quit
^C/usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/autotest.rb:
131:in `initialize': wrong number of arguments (0 for 1)
(ArgumentError)
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:131:in `exception'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:131:in `raise'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:131:in `add_sigint_handler'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:274:in `call'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:274:in `sleep'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:274:in `wait_for_changes'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:101:in `get_to_green'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:84:in `run'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:82:in `loop'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:82:in `run'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:62:in `run'
        from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/bin/
autotest:45
        from /usr/local/bin/autotest:16:in `load'
        from /usr/local/bin/autotest:16

Anyone know if this is a bug or am I exiting the program improperly?

Thanks once again to the great Ruby community for coming up with such
cool stuff.
Robert
    
>

Hitting Ctrl-C should interrupt autotest and run all the tests from the
top (not just what you've just changed). Hitting Ctrl-C twice, should
exit autotest entirely. Are you seeing some other behaviour?

Chris

The only other behavior I'm seeing that the attached errors displayed
in the terminal window when hitting ^C the second time. It exits
fine, just not cleanly.