Hugh, > I would prefer that the output is not through divs but is returned > directly to Selenium as strings. > A quick reply to this detail: Your understanding of Selenium might be ahead of mine, but I thought the primary focus of Selenium was interacting with the DOM. You usually trigger some browser action and then inspect the resulting page (DOM). Therefore the divs. I know there is this assertEval etc. infrastructure for evaluating Javascript code, but my impression so far was it is more of an aside and I haven't really investigated how far you could get with it. Your suggestion would build on this infrastructure entirely.
Another point: In my understanding, unit test do *not* return a value. They either succeed silently or throw an exception. I think JsUnit works this way, and we designed our unit test protocol corresponingly (We even supported running TestRunner tests from a JsUnit framework). If you start adding return values to your tests you're leaving the confines of this protol and are entering a completely new testing realm. Thomas ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
