[Windmill-dev] JS error handling
Matthew Eernisse
mde at osafoundation.org
Thu Dec 13 21:33:09 PST 2007
Howdy.
I've recently made some improvements to the error handling in the JS
tests. Okay, to be honest, I've *added* error handling. :) It's way less
painful now (even in IE :)) when something goes south while you're
writing JS tests.
Now that we're getting parse errors and suchlike from the loaded JS test
code in a place where we can do something with them, what do we want to do?
I'm actually finding now that I'm getting just about as much info about
these errors as I need right in the Output tab, and don't find myself
looking in Firebug (it's eval'd code anyway, so line numbers are
currently worthless).
It might be nice to add a developer option for not rethrowing the error,
and actually starting the event loop again.
That would mean that parse or execution errors in loaded JS test code
wouldn't require a reload of the IDE. You could fix the error in your JS
test code, and just run the tests again.
Thoughts?
Matthew
More information about the Windmill-dev
mailing list