javascript errors - getting them programatically about capybara-webkit HOT 8 CLOSED

I think the desired default behavior would be to raise an exception if a page loaded with a Javascript error, but I haven't figured out how to do that yet with Qt's WebKit.

from capybara-webkit.

That would be nice. Specially to trace issues in Javascript intensive web-apps, i.e: there is a javascript error that prevents my app from loading in capybara-webkit. Having that would help me to solve the compatibility problem.

@jferris Have you figured something out about this?

Thanks :D

from capybara-webkit.

I would love this as well. JS errors are logged in the test output, but I can't figure a way to get access to them within the page.

I have this in my output:

http://127.0.0.1:51777/test:171 ReferenceError: Can't find variable: adsfasdfdsafdsa

And ideally I'd like to be able to write something like this in my test:

page.javascript_errors.should be_empty

Possible?

from capybara-webkit.

I haven't found a way to explicitly get Javascript errors, but we could
return all the messages written to the console in a command. This would
include messages printed using console.log, but I don't think that would be
an issue.

If anybody wants to put together a pull request, it would involve saving
messages in WebPage::javaScriptConsoleMessage and a new command to return
them.

from capybara-webkit.

Just sent a pull request for this. I have it working in one of my own projects. Please let me know if there's anything I need to change. Thanks!

from capybara-webkit.

Is there anyway currently to get more information about the error? I occasionally get things like:

undefined:0 TypeError: 'null' is not an object

And I assume its undefined:0 because its coming back in an AJAX request, but I'm having a hard time tracking these types of errors down. Even having the line where the error occurred spit out would be great.

from capybara-webkit.

There isn't a way through the current API. There may be a way to get more information from QtWebkit. If you find one, feel free to submit a pull request.

from capybara-webkit.

Since this isn't a bug and it's something we've been striving for I'm going to close this. In the future we hope to have better JS error support.

from capybara-webkit.