Open h0jeZvgoxFepBQ2C opened 11 years ago
See also here (no answer at the moment, but 5 people voted for it):
I'm also having this issue. Is there already a solution? What can I do to debug this problem?
no i didnt found anything unfortunately :/
I'm also having this issue...
Added also an issue on the capybara github page https://github.com/jnicklas/capybara/issues/1086
RDX posted following on stackoverflow:
Somehow your STDOUT is getting replaced with some other buffer. So whatever is being written by Capybara to STDOUT is getting ignored or consumed somewhere else.
Try the following:
# Add global before/after blocks
before :each do
@old_stdout, @old_stderr = STDOUT, STDERR
end
after :each do
STDOUT, STDERR = @old_stdout, @old_stderr
# Some gems use $stdout and $stderr, instead of STDOUT and STDERR, replace those too
$stdout, $stderr = @old_stdout, @old_stderr
end
Capybara's save_and_open_page uses Launchy gem. So I believe the STDOUT and STDERR are getting stubbed in one of these gems.
I'm having the same issue. It seems like it is still running in the background, its just that nothing after the save_and_open_page
gets printed, until you restart guard in my case.
When i run my rspec tests with spork, every time i use capybara's save_and_open_page, spork is loosing the test suite.. or maybe doesnt output anything anymore...
See the log
Any suggestions?