You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change your Konacha configuration to be something like:
Konacha.configure do |config|
Capybara.register_driver :selenium_marionette do |app|
Capybara::Selenium::Driver.new(app, browser: :firefox, marionette: true)
end
config.driver = :selenium_marionette
end if defined?(Konacha)
Run
Upon running, however, even though the test, in the browser runs correctly, I now get, from the command line: ERROR - Error communicating with browser process: TypeError: window.top.Konacha is undefined
Somehow, the context in which the session scripts execute is not the same as the ones where the JS files are loaded so a console.log(window.top.Konacha); in the runner.js and in the runner.rb yield different results. The former is correct. The latter is undefined.
The text was updated successfully, but these errors were encountered:
Due to a problem with Firefox 47, Konacha tests don't report correctly
to the command line. Issue is
jfirebaugh/konacha#228.
While it is not fixed, using chromedriver. To use firefox 47, simply use
the selenium_marionette driver for Konacha in the initializer.
Firefox 47 is only compatible with the marionette webdriver (https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver).
Selenium needs to be configured to use such driver. Mainly it is:
chmod +x wires
. Put it on your path.Upon running, however, even though the test, in the browser runs correctly, I now get, from the command line:
ERROR - Error communicating with browser process: TypeError: window.top.Konacha is undefined
Somehow, the context in which the session scripts execute is not the same as the ones where the JS files are loaded so a
console.log(window.top.Konacha);
in therunner.js
and in therunner.rb
yield different results. The former is correct. The latter isundefined
.The text was updated successfully, but these errors were encountered: