search

david850067064 / as3flexunitlib

Automatically exported from code.google.com/p/as3flexunitlib
0 stars 0 forks source link

Capturing Exceptions is frustrating. #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set up a test suite 
2. Run in debug mode
3. On encountering exception, exception shown in TestRunnerBase

What is the expected output? What do you see instead?
I see what is expected. However when im running in debug, i'd like to 
catch the exception in the Flex debugger and not TestRunnerBase. So far, 
I've explicitly encountered this issue with null reference assignments.

What version of the product are you using? On what operating system?
.85 - WinXp

Please provide any additional information below.
An option to not catch all exceptions would suffice.
I use the unit tests to test my code well before I have any other 
mechanism for using it. When the Runner catches the exception and shows 
it, it robs me of my ability to see the state of the app and to have the 
line where the problem occured highlighted.

Original issue reported on code.google.com by Squee...@gmail.com on 26 May 2007 at 11:23

GoogleCodeExporter commented 9 years ago 
I have the same problem.  It is very difficult to develop with as I am using 
test
driven development.

Is there a custom error class for failing tests? If so i do not mind catching 
them in
my code and bubbling them up to the test runner.

Original comment by eamonn.f...@gmail.com on 5 Aug 2008 at 7:17