Hi I've just installed a trial version of The Welkin Suite and I've been having a look at the debugging functionality for unit tests. I have a unit test class including tests that check for exceptions being thrown from particular methods (the exceptions thrown are of our own in-house Exception types that we have subclassed and deployed to our environment). I am wanting to debug one of our other test methods that don't involve exceptions being thrown and unfortunately it seems in order to debug unit tests the debugging session has to run all unit tests in the test class.
Before I get to hit my breakpoints in the specific test I want to debug, a dialog appears and the code breaks at the throwing of the exception within one of the other tests in the test class. Despite the unit tests catching the exception thrown the debug session exits on continuing (even pressing F10 to step to next line the debug session will progress to the catch clause but then exit when pressing F10 again to go into the catch clause block). This means I need to comment out a block of unit tests in order to successfully hit my breakpoints in the test I'm interested in debugging which isn't ideal (it would be nice to be able to debug a single unit test similar to how you can execute a single unit test within a test class, I did see another bug from someone with a title that looks like it's raised this point but if you'd like me to raise a separate issue for this I will as it would be very handy).