ZenTest


#1

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:inexception’
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:inadd_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:insleep’
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:inget_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:inloop’
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:inrun’
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


#2

So does anyone have any ideas about this?


#3

Robert W. wrote:

But, I did notice one very minor thing. When I use ^c to stop the
from /usr/local/lib/ruby/gems/1.8/gems/ZenTest-3.4.3/lib/
autotest.rb:84:in `run’

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

http://www.autopendium.co.uk :: stuff about old cars


#4

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.