Thomas,

Sorry about the delay in replying.

> Look, I'm not talking TestRunner right now, not even qooxdoo. I was 
> refering to the Selenium log, which you have mentioned as well. All 
> I want to get is a clear picture how you envision that a Selenium 
> client driver script (think: Python) interacts via SRC with 
> Javascript code in a web app.

Either calling individual tests or using a runAll() function as you
suggested below. runAll() could take a spec for the functions to test,
maybe as a regular expression and any function names that match would be
called.

We need to provide feedback on what tests have been run and what the
result was. Perhaps for any test we could have a tuple of (test function
name, boolean result, failure message, log). Then if multiple tests are
run as a result of a function call it would give a list of these results.

The log would be the qooxdoo log messages which might include some
debugging output, useful for finding what's going on. Send it as one long
string but make it easy to parse by splitting on newline, comma etc.
 
> > 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.
> 
> That's a bit too much "big picture" for my taste at the moment. 
> Let's focus on the topic above.

Indeed - I would see that as our responsibility. If we can just get the
log of tests that have been carried out and any results into our Python
code I would be happy. Then we can email etc from there.
 
> > 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.
> 
> I figure you would try and put sufficient information in the 
> exception thrown, right?!

Yes, my bad - I hadn't seen the msg parameter to the test functions. I've
withdrawn the bug.

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

Reply via email to