rspec users - Apr 2009 - Autospec stops running after tests are complete

I installed an app template into an existing rails install. In the process I
upgraded to RSpec 1.2.2 and I''m running Rails 2.3.2.

Now autospec will run once and then exit. Returning me to the CLI prompt.

Any ideas?

Thanks!
-- 
View this message in context:
http://www.nabble.com/Autospec-stops-running-after-tests-are-complete-tp22829288p22829288.html
Sent from the rspec-users mailing list archive at Nabble.com.

I''m thinking now the problem may be ZenTest 4.0. I reverted back to
3.11 and
it was working there. But 3.11 has conflicts with Rails 2.3.2 and I need to
run rails. Still need help if anybody has some for me.

Thanks again.


rosentraterds wrote:
> 
> I installed an app template into an existing rails install. In the process
> I upgraded to RSpec 1.2.2 and I''m running Rails 2.3.2.
> 
> Now autospec will run once and then exit. Returning me to the CLI prompt.
> 
> Any ideas?
> 
> Thanks!
> 
-- 
View this message in context:
http://www.nabble.com/Autospec-stops-running-after-tests-are-complete-tp22829288p22830431.html
Sent from the rspec-users mailing list archive at Nabble.com.

Maybe related. When I try to run RSpactor (since autospec isn''t
working) it
only runs 1 example.

Still no solution.


rosentraterds wrote:
> 
> I''m thinking now the problem may be ZenTest 4.0. I reverted back
to 3.11
> and it was working there. But 3.11 has conflicts with Rails 2.3.2 and I
> need to run rails. Still need help if anybody has some for me.
> 
> Thanks again.
> 
> 
> rosentraterds wrote:
>> 
>> I installed an app template into an existing rails install. In the
>> process I upgraded to RSpec 1.2.2 and I''m running Rails 2.3.2.
>> 
>> Now autospec will run once and then exit. Returning me to the CLI
prompt.
>> 
>> Any ideas?
>> 
>> Thanks!
>> 
> 
> 
-- 
View this message in context:
http://www.nabble.com/Autospec-stops-running-after-tests-are-complete-tp22829288p22832758.html
Sent from the rspec-users mailing list archive at Nabble.com.

SOLVED:

OK the problem was coming from Carlos Brando autotest-notification 1.9.0. It
had to do with invalid checking of constants. Testing SUCCESS_SOUND.empty?
instead of const_defined?("SUCCESS_SOUND").

I''ve fixed it in my fork.
http://github.com/marcusrosentrater/autotest-notification/tree/master

And sent a pull request to Carlos Brando and Team.


-- 
View this message in context:
http://www.nabble.com/Autospec-stops-running-after-tests-are-complete-tp22829288p22834751.html
Sent from the rspec-users mailing list archive at Nabble.com.