Hallo Michael, > ... >> to 2) >> prototype's unit tests have been integrated with the idea to make >> htmlunit "prototype compatible" and to run these tests within htmlunit's >> tests to ensure that this is the case. Currently 4 of the test "suites" >> are working and 8 are failing. From the 8, 2 fail due to issues in Rhino >> (in fact one issue has been rejected because the feature is not required >> by the ECMA spec). Concerning the 6 other, I've an idea of probably the >> main problem cause but my flight last week wasn't long enough to let me >> investigate it in details. Roughly: htmlunit doesn't build a prototype >> hiearchy. Quite bad for... prototype. > > What do you mean with hiearchy? Does it mean htmlunit can not at all, or > by now (but probably will in future ;-) )? Where can I find these tests?
in fact htmlunit mis-uses Rhino: in JavaScript if a property/method is not found on an object, the object's prototype is looked and so on. htmlunit doesn't define methods and properties the right way and each object intercepts the calls by itself. This is what prototype relies on in FF. Btw, it could be interesting to investigage how prototype runs when simulating IE. Currently it "thinks" that browser is FF because prototypes are available but it would be easy to hide them. I will try to add a test (as notYetImplemented()) illustrating the problem. If you look at the htmlunit-dev mailing list, you will be notified once it's committed. > >> Once you've found something with a WebTest, it may be useful to strip it >> down to htmlUnit unit test. This makes debugging and integration in >> htmlunit easier. >> >> Btw. do you have a customized version of htmlUnit? I don't recognize >> some of the log outputs. > [...] > I don't think so, I used my webtests build from source including the > actual (build from source) htmlunit.jar. Thats it ;-). > > Which of the log outputs do you mean, in detail? > ups, sorry, these are warnings generated by Rhino: WARN (com.gargoylesoftware.htmlunit.ScriptEngine) - warning: message=[Calling eval() with anything other than a primitive string value will simply return the value. Is this what you intended?] sourceName=[http://bendera:8888/adds/prototype-1.4.0.js] line=[700] lineSource=[null] lineOffset=[0] Marc. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
