I try to debug an http integration test, which normally runs outside (local) testrunner due to a filter I have set up on "Test filter" for this machine.
However processing queue only states "Pending" when I try to debug it, i.e. it does seem to wait for it to be started on remote machine where it can be run?
Shouldn't NCrunch ignore the test filter during debugging, how can I otherwise debug it?
Thanks.
*Edit: Weird, I cannot even run it when modifying the filter so it should no longer prevent it. Bug report submitted, trying with a vstudio restart.
*Edit2: The "Test filter builder" takes about 16s to be displayed :/
*Edit3: Restarting vstudio did it, is the filter cached in some way?
Debug tests can only be run on the local machine. This may explain why the test was stuck in the queue - the Test filter prevented it from running, so it just stayed there.
I've just managed to reproduce the problem with the Test Filter not updating. This is probably a regression caused by the engine separation. Restarting the IDE does cause it to update itself again from the configuration. I'll see if I can get this fixed.
When the test filter builder took 16 seconds to show, was the engine doing any processing? Sometimes when the core engine thread is overloaded, it can become unresponsive to requests from the UI.
Remco wrote:Debug tests can only be run on the local machine. This may explain why the test was stuck in the queue - the Test filter prevented it from running, so it just stayed there.
Wouldn't it make sense to automatically "ignore" those filters when debugging is requested?
Remco wrote:
When the test filter builder took 16 seconds to show, was the engine doing any processing? Sometimes when the core engine thread is overloaded, it can become unresponsive to requests from the UI.
No it takes that every time, actually it takes 16 for the dialog to show, and 21s to complete "loading".
Test filter is not that complicated I think: http://screencast.com/t/4HhiXJ0W
GreenMoose wrote:
Wouldn't it make sense to automatically "ignore" those filters when debugging is requested?
Yes. I'll look into this.
GreenMoose wrote:
No it takes that every time, actually it takes 16 for the dialog to show, and 21s to complete "loading".
Test filter is not that complicated I think: http://screencast.com/t/4HhiXJ0W
That's definitely not right. I'll see if I can reproduce this and will get back to you.