|YaK:: WebLog #535 Topic : 2007-08-16 08.33.20 matt : more iframe JsUnit testing suckage||[Changes] [Calendar] [Search] [Index] [PhotoTags]|
|[Back to weblog: pretention]|
In our JsUnit tests, we created the JS object, got the custom render function for the given column element, called it, and then executed the onclick() handler for said element. (There were some assertions as well, but the code didn't get that far.) Firefox gave a really obtuse error:
[Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIDOMHTMLIFrameElement.src]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:////home/matt/src/projectX/js/searchResultRow.js :: anonymous :: line 29" data: no]
Our custom renderer modified the "src" property of an IFRAME element, which immediately causes the browser to try and load the new src into said IFRAME. Because we were running locally, it was looking for the src on the local hard drive. It didn't find the src, so Firefox vomited up the aforementioned obtuse error.
We ended up testing it using Selenium , which is at least an order of magnitude slower than our JsUnit test. Selenium has its place, but JsUnit tests can provide more precise and actionable information about a test failure more quickly than Selenium can. This is mostly because JsUnit tests are generally written at the more granular unit-test level, whereas Selenium tests are generally written at the less granular system-test level. They're both awesome tools and they both have their place.
Yet another reason to avoid IFRAMEs, in my opinion. If I'm missing something that would allow us to unit test the modification of an IFRAME src property, someone please let me know.
Discussion:showing all 0 messages
|(last modified 2007-08-27) [Login]|