Do you have any files, which might be changed during your failing
tests? Some temporary files or whatsoever? If that’s the case, then
autotest thinks that you have made some changes already and tries to
run again. Solution would be to put that file into ignore list for
autotest.
Do you have any files, which might be changed during your failing
tests? Some temporary files or whatsoever? If that’s the case, then
autotest thinks that you have made some changes already and tries to
run again. Solution would be to put that file into ignore list for
autotest.
No… all was working some days ago.
in fact the same issue occurs with a new fresh project. Here is my test
On 12 jun 2009, at 13:42, Alexandre Da Silva wrote:
Jarmo P. wrote:
Do you have any files, which might be changed during your failing
tests? Some temporary files or whatsoever? If that’s the case, then
autotest thinks that you have made some changes already and tries to
run again. Solution would be to put that file into ignore list for
autotest.
No… all was working some days ago.
I have the same issue. Whether a red rspec or cucumber file, autotest
goes beserk.
Using the latest and greatest gems, on a fresh rails app.
On 12 jun 2009, at 13:42, Alexandre Da Silva wrote:
Jarmo P. wrote:
Do you have any files, which might be changed during your failing
tests? Some temporary files or whatsoever? If that’s the case, then
autotest thinks that you have made some changes already and tries to
run again. Solution would be to put that file into ignore list for
autotest.
No… all was working some days ago.
I have the same issue. Whether a red rspec or cucumber file, autotest
goes beserk.
Using the latest and greatest gems, on a fresh rails app.
gr,
bartz
it seems that many people are getting the same,
at least for me and all developers from my two teams.
yesterday I realise that when I have green results, then I modify my
controller files, than rspec does not auto restart the tests.
does anyone else having the same behavior?
On Jun 13, 2009, at 11:19 PM, Alexandre Da Silva wrote:
I just copied this all into a shell and the specs ran only once and
Also, I tried this with and without some autotest exceptions set up
Source one: remarkable gem
if you use remarkable, try do uninstall that gem and test if the
testes
continue looping
Source two: localized_dates plugin
if you use this plugin try removing it and run the tests again. I mean
that localized_dates plugin is not needed in rails 2.3.3 anymore.
I don’t have these plugins or gems, but I found out that downgrading
ZenTest to version 4.0.0 solved the problem.
I just copied this all into a shell and the specs ran only once and
stopped, as expected.
rspec-1.2.6
rspec-rails-1.2.6
ZenTest-4.1.1
Mac OS 10.5.7
ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
Anything different in your environment?
Also, I tried this with and without some autotest exceptions set up in
my ~/.autotest file, and it worked correctly in either case.
gems are the same… but I have a lot of other gems. I tested removing
all gems and reinstaling one by one… after all gems installed (except
remarkable gem) the test above ran as expected.
After some inspects I found in different projects two possible sources
of the problem.
Source one: remarkable gem
if you use remarkable, try do uninstall that gem and test if the testes
continue looping
Source two: localized_dates plugin
if you use this plugin try removing it and run the tests again. I mean
that localized_dates plugin is not needed in rails 2.3.3 anymore.
rails blogapp
rspec-rails-1.2.6
gems are the same… but I have a lot of other gems. I tested
if you use remarkable, try do uninstall that gem and test if the
to version 4.0.0 solved the problem.
Did you install the autotest-rails gem per the ZenTest 4.1 release
notes?
Of course not :).
I just ran sudo gem update :).
Will check, and report back though.
gr,
bartz
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.