Agreed.
And the more I use Pharo, the more I am looking into tests (especially
"Debug Test" to understand how things do work) and writing tests first.
That's not a natural thing to do in other environments but feels so great
to do in Pharo.
(Writing this after having looked at a ton of Seaside a
On 17 nov. 2013, at 15:16, Tudor Girba wrote:
> I stumbled across this idea when Markus Gaelli chose it as a PhD topic about
> ten years ago (man, I'm old). The main idea was not to provide tests, but
> examples that happened to have assertions. The goal was twofold: (1) provide
> live docume
Ok guys, in the end I implemented a big time clutch that simulates the
behaviour I was after:
I created a tiny app in C++ that starts Pharo, the image reads the --serve
flag (that I implemented in DefaultCommandLineHandler), hides itself via
NB, and kills the UIManager process to prevent refreshes
I don't like having the Unit Tests so coupled with the code.
Many times I implement Unit Tests that doesn't match 1:1 with a class.
It is... the TestCase subclass doesn't have a corresponding class (eg.
SomeFeatureTest, with no SomeFeature class in the system).
Regards,
Esteban A. Maringolo
2
On 18 nov. 2013, at 13:07, Esteban A. Maringolo wrote:
> I don't like having the Unit Tests so coupled with the code.
>
> Many times I implement Unit Tests that doesn't match 1:1 with a class.
> It is... the TestCase subclass doesn't have a corresponding class (eg.
> SomeFeatureTest, with no So
Esteban,
good point. I use Tests sometimes as a mixture of design help and living
documentation. And there, test cases almost never match classes 1:1.
And I also think that is a good thing. Especially when it comes to
refactoring and major redesign where the API of some entry points to a
certa
Cmd+ click on a class jumps there.
On Nov 17, 2013, at 10:43 PM, Juraj Kubelka wrote:
> Hi,
>
> this week I have realized a lot of useful (hidden) features I did not know
> they exists. Those I have learned:
>
> Cmd+t — Nautilus, when method source code is displayed. It shows context menu
>
quite cool!
Stef
On Nov 18, 2013, at 11:25 AM, Bernat Romagosa
wrote:
> Ok guys, in the end I implemented a big time clutch that simulates the
> behaviour I was after:
>
> I created a tiny app in C++ that starts Pharo, the image reads the --serve
> flag (that I implemented in DefaultCommand
+1
>
> One could now start a new discussion on whether this use case is "unit
> testing" or now, but I guess we can be glad when people write any kind of
> test ;-)
> Not every thing that should be improved can be improved by changing tools.
> Sometimes it really is a people thing.
On 18 Nov 2013, at 21:58, Stéphane Ducasse wrote:
> Cmd+ click on a class jumps there.
Or on a method.
> On Nov 17, 2013, at 10:43 PM, Juraj Kubelka wrote:
>
>> Hi,
>>
>> this week I have realized a lot of useful (hidden) features I did not know
>> they exists. Those I have learned:
>>
>>
Or on an instance variable
On Mon, Nov 18, 2013 at 11:02 PM, Sven Van Caekenberghe wrote:
>
> On 18 Nov 2013, at 21:58, Stéphane Ducasse
> wrote:
>
> > Cmd+ click on a class jumps there.
>
> Or on a method.
>
> > On Nov 17, 2013, at 10:43 PM, Juraj Kubelka
> wrote:
> >
> >> Hi,
> >>
> >> this
Not on Windows. Alt-Click doesn't work either.
What works is select the word and Ctrl-Enter to jump.
Annoying discrepancy...
Phil
On Mon, Nov 18, 2013 at 9:58 PM, Stéphane Ducasse wrote:
> Cmd+ click on a class jumps there.
>
> On Nov 17, 2013, at 10:43 PM, Juraj Kubelka
> wrote:
>
> > Hi,
>
Phil wrote:
>Not on Windows. Alt-Click doesn't work either.
>What works is select the word and Ctrl-Enter to jump.
Did you try "Alt" + right mouse click on a class to jump.
Works for me.
Thx
T.
Wow, thank you all. So in order to summarize:
Cmd+click on instance variable — it opens window “Accesses to variable"
Cmd+click on method — it opens implementors of the method
Cmd+shift+click on method — it opens senders of the method (on method
definition reversely)
Cmd+click on Class — it ope
14 matches
Mail list logo
