[wingide-users] testing tab and drilling to exceptions
andyaltepeter at invenshure.com
Tue Dec 15 15:33:43 EST 2015
Thanks for your fast response! What you proposed sounds good to me. I
don't know whether I would click the "x" very often and would probably
prefer the full exception line since it's a larger click area.
Is there a setting in Wing where the exception traceback can be left
expanded when only running a single test? I Generally I write tests and
make sure they pass, so I'm re-running the same test over and over, and the
exception is always collapsed. Or maybe subsequent test runs could
remember the expand-state of the prior run? I get that expanding every
exception when running many tests would be overwhelming and a poor
Andy Altepeter | Software Architect
227 Colfax Ave. N., Suite 148
Minneapolis, MN 55405
O: 612.520.7361 x2131
On Tue, Dec 15, 2015 at 9:57 AM, Wing IDE Support <support at wingware.com>
> On 12/15/15 9:23 AM, Andy Altepeter via wingide-users wrote:
>> I would like to quickly drill to the line in the test that failed.
>> I haven't found it at all useful to drill into the assertX methods in
>> the unittest stdlib. Could the behaviour of the test tab instead link
>> to the line in my test that failed?
> I agree that it should be easier to get to the exception and that Wing
> should not drill into the assertX methods. Going to the exception should
> be put on the right-click popup menu and be the default action when the
> exception: line is double-clicked, but I don't think it should be the
> double-click action on the test name because that is used to go to the test
> source regardless of if it failed or not. Probably, Wing should go to the
> exception if the failure icon is double-clicked, but not if the name is
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the wingide-users