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 tracker if there is something about that, but I was not able to find it. I entered in the search input field the tree keywords: test button nautilus The result is https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus However, this indicates many closed issues. How can I filter out the close issues? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
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 <[hidden email]> wrote: Hi! |
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 :
smime.p7s (5K) Download Attachment |
> On 11 Sep 2015, at 16:37, Christophe Demarey <[hidden email]> 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 cleanup, it was removed. > Yes, I removed that double runnning.. this was not a good idea. Now it is much simpler. And yes, it is better to directly open the debugger when running single tests explicitly. I will fix it. Marcus |
In reply to this post by abergel
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 able to find it. I entered in the search input field the tree keywords: test button nautilus > The result is https://pharo.fogbugz.com/f/search/?sSearchFor=test+button+nautilus > 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. You can, though, filter the search results. Press “+Refine Further”, there are many things, amount them “Open or Closed”. Select Open. Marcus |
Excellent!
Thanks ! Works! Alexandre > On Sep 11, 2015, at 2:43 PM, Marcus Denker <[hidden email]> 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. > > You can, though, filter the search results. Press “+Refine Further”, there are many things, amount them “Open or Closed”. Select Open. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
In reply to this post by Marcus Denker-4
Thanks! That would be fantastic.
Alexandre > On Sep 11, 2015, at 2:40 PM, Marcus Denker <[hidden email]> wrote: > > >> On 11 Sep 2015, at 16:37, Christophe Demarey <[hidden email]> 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 cleanup, it was removed. >> > Yes, I removed that double runnning.. this was not a good idea. Now it is much simpler. > > And yes, it is better to directly open the debugger when running single tests explicitly. > > I will fix it. > > Marcus > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. |
Free forum by Nabble | Edit this page |