the left hand side of the method name. If the test fail, it does not open a
debugger. I need to run it a second time. This is a rather odd behavior.
> Am I the only one to experience this?
>
> Side question:
> I try to check on the bug tracker if there is something about that, but I was
> not
Excellent!
Thanks ! Works!
Alexandre
> On Sep 11, 2015, at 2:43 PM, Marcus Denker wrote:
>
>> However, this indicates many closed issues. How can I filter out the close
>> issues?
>>
> Yes, it is annoying that the default for the search is to search closed
> issues.
Thanks! That would be fantastic.
Alexandre
> On Sep 11, 2015, at 2:40 PM, Marcus Denker wrote:
>
>
>> On 11 Sep 2015, at 16:37, Christophe Demarey
>> wrote:
>>
>> I do experience the same thing with Guille today.
>> Before, Nautilus ran
>
> If the test fail, it does not open a debugger.
This happens when I click on the button next to the _class_, however I've
never experienced such problem with the button next to a _method_.
Peter
On Fri, Sep 11, 2015 at 4:21 PM, Alexandre Bergel
wrote:
> Hi!
>
> I
I do experience the same thing with Guille today.
Before, Nautilus ran twice the method for a failed test: one to get the status
of the test and another one for the debugger.
Maybe in Nautilus cleanup, it was removed.
Le 11 sept. 2015 à 16:34, Peter Uhnák a écrit :
> If the test fail, it does
Hi!
I can run a test method by pressing the button located on the left hand side of
the method name. If the test fail, it does not open a debugger. I need to run
it a second time. This is a rather odd behavior.
Am I the only one to experience this?
Side question:
I try to check on the bug
> On 11 Sep 2015, at 16:37, Christophe Demarey
> wrote:
>
> I do experience the same thing with Guille today.
> Before, Nautilus ran twice the method for a failed test: one to get the
> status of the test and another one for the debugger.
> Maybe in Nautilus