[Windmill-dev] JS error handling

[Mikeal Rogers]

This brings up another issue I've been mulling over.

I don't _ever_ use the windmill debugging option ( as passed to the  
windmill bin ). There is so much information spewing out from the  
debugging logger that the option is basically useless.

I'm wondering if we should repurpose this option. We've already added  
an option for "browser debugging" which means loading the tests in to  
the IDE rather than running them, blocking in python until they  
return, and ending tests in each test method/json file once we hit a  
failure.

Maybe it would be a worthwhile exercise to run through all of the on/ 
off debugging options we have in both the Service and the IDE.

-Mikeal

On Dec 13, 2007, at December 13, 20079:42 PM, Adam Christian wrote:

> I totally agree, if you look in the IDE options in the latest  
> release, I have added a check box to rethrow the errors. I have also  
> defaulted the fleegix debugging to true.
>
> If in the future we want a command line option to turn on this  
> debugging 'mode' it should be trivial.
>
> Adam
>
> On Dec 13, 2007, at 9:33 PM, Matthew Eernisse wrote:
>
>> 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
>> _______________________________________________
>> Windmill-dev mailing list
>> Windmill-dev at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>
> _______________________________________________
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/windmill-dev