> I presume you are also not very interested in the Selenium log, when > you can have all the evaluation (and therefore logging) in the > client driver, right?!
Actually, the client log isn't particularly good at the moment in TestRunner. In IE a popup is used (which has security problems when running from a local directory). Nothing appears in the TestRunner log. I suppose http://bugzilla.qooxdoo.org/show_bug.cgi?id=410 might cover this. And I would want all the log output to be in one place. Ultimately we would want to capture the complete log including black box tests, unit tests and white box tests and automatically email it to relevant parties. We do that at the moment for Python unit tests, picking out functions that have failed and highlighting them. I've raised a few bugs on the TestRunner this morning; some of which are relevant for the Selenium interface (for example, how do you determine which part of a unit test has failed when there are 20 or so function calls in one unit test function. By the way, despite all my complaining, the unit test functions that I've written for my low level routine *have* been very useful. They quickly showed up a situation that wasn't handled properly. So thanks for putting the initial framework in place for these! Hugh ------------------------------------------------------------------------- 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
