"Ruby Interpreter (CUI) 1.9.3p194 [i386-mingw32] has stopped working" error when running in IE #714

Closed
jsmiley opened this Issue May 21, 2012 · 14 comments

3 participants

@jsmiley

I run the code using the chrome driver <--- works correctly with no errors

I run the code using the IE driver <---- fails every time with the subject error message.

I am just trying to test a website I have deployed locally (URL = localhost)

I am testing using the following settings:

Capybara.run_server = false
Capybara.default_selector = :css
Capybara.default_wait_time = 30

Capybara.register_driver :selenium_with_long_timeout do |app|
client = Selenium::WebDriver::Remote::Http::Default.new
client.timeout = 300
Capybara::Selenium::Driver.new(app, :browser => :internet_explorer, :http_client => client, :resynchronization_timeout => 60)
end

Capybara.javascript_driver = :selenium_with_long_timeout
Capybara.default_driver = :selenium_with_long_timeout

I am not sure why I am getting this error but since it is working correctly in Chrome but not in IE it seems like a bug.

@joliss
Collaborator

This is almost certainly not a bug in Capybara, but in the Selenium driver.

See if you can reproduce it with this template: https://gist.github.com/1024843
Then send the bug report to @ jarib, or file a report in the Selenium bug tracker.

@joliss joliss closed this May 21, 2012
@jsmiley

I am confused, what am I supposed to do with this template?

@joliss
Collaborator

The template exercises the selenium-webdriver gem, which is the library that Capybara forwards all your calls to as well. Edit the template until it crashes the same way your larger app crashes. That way you have a one-page snippet to send as a bug report.

(You'd probably use :internet_explorer, and if necessary fill in code after begin, and set up any HTML that's necessary to trigger the crash.)

@joliss
Collaborator
@jsmiley

just add visit "localhost" and there you go.

@jsmiley

Doesn't get past the "default webdriver page" page

@jnicklas
Owner

@jsmiley if you're writing a bug report you need to be as explicit as possible. Now this bug doesn't really concern Capybara, but if I were Jari, I would probably need way more information than you've given us here. Remember, these are bug trackers, not support forums, it's not our responsibility to figure out what issue you are having. The template is there to guide you in writing something the Selenium guys can use to help you.

@jsmiley

let me rephrase my problem.

How do I use this template to provide useful info? Where does this go in the code? (first time ever being asked to do something like this)

@jnicklas
Owner

@jsmiley it's not so much about the template itself, as isolating the problem. That's what the template is useful for. Run it, verify that it works, then modify it so it more closely resembles how your code looks, until you can come up with the most minimal set of conditions for creating the error you're experiencing.

@jsmiley

@jnicklas, it will never work. DATA doesn't exist.

@jsmiley

I also believe that the template is not designed to debug a cucumber test script.

@jsmiley

Also, one last thing, it never gets to my code!!!!! It even finishes executing my env file. There is something happening in a layer I do not have access to.

@jnicklas
Owner

You have access to all layers. Capybara is open source, Selenium is open source, Cucumber is open source, hell even Ruby is open source. And it's never a bug in the operating system, that's a fundamental principle of debugging ;) Start digging! Start removing layers! Debug!

@jsmiley

Alright, I gotcha, I didn't realize you wanted me to debug the cucumber project and my test project (thought you were looking for some sort of function under the hood which is throwing the issue)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment