Dolphin 5 at Smalltalk Solutions

> Chet Hendrickson and I will be doing a pair programming / test-driven design
> session. I think Ann Anderson will be there as well.
>
> Thanks to a special arrangement with Object Arts, we'll be doing the
> demonstration using Dolphin Version 5, with the refactoring browser!
>
> We'll describe a small problem, think about a design, then develop the program
> test-first. We'll be demonstrating radically frequent use of SUnit, refactoring
> as we go, and then we'll take questions and discussion of the techniques, the
> result, and what they may mean to your work.
>
> Chet, Ann, and I will be there to have a good time. Come along and help, and see
> the new Dolphin 5 in action.
>
> Ronald E Jeffries
> http://www.XProgramming.com
> http://www.objectmentor.com
> I'm giving the best advice I have. You get to decide whether it's true for you.

> On Thu, 18 Apr 2002 07:11:05 -0400, Jeffrey Odell <[hidden email]> wrote:
>
>
>>Will you be using the SUnit Browser?  At least then I'll be there in
>>spirit ;>
>
>
> Ah, my brain engaged. I know what it is. I'll see if we can use it ... not sure
> it'll fit the flow but what the heck ...
>
> Ronald E Jeffries
> http://www.XProgramming.com
> http://www.objectmentor.com
> I'm giving the best advice I have. You get to decide whether it's true for you.

> On Sat, 20 Apr 2002 11:54:08 -0400, Jeffrey Odell <[hidden email]> wrote:
>
>
>>If your XP session includes running the original SUnit UI, then this one
>>should work for you as an enhanced browser for SUnit.  Unfortunately I
>>won't be there, but it should be plug compatible with your tests, and if
>>it is not I'd sure like to fix that.
>>
>>I think this browser helps doing XP, and I'd really benefit from your
>>take on it if you get a chance to use it.  I'd like to keep improving it
>>over time.
>
>
> Are we talking about the same thing? The browser that has a list of the test
> classes, and the little list of how they scored, a run button, the list of
> methods over on the right?
>
> It's interesting but I'm not sure just how it helps me moment to moment. Tell me
> a bit about how you use it?
>
> Ronald E Jeffries
> http://www.XProgramming.com
> http://www.objectmentor.com
> I'm giving the best advice I have. You get to decide whether it's true for you.

>Hi Ron,
>
>> It's interesting but I'm not sure just how it helps
>> me moment to moment. Tell me a bit about how
>> you use it?
>
>I have been using Jeffrey's SUnit Browser, and I do find it easier to use
>for
>the following reasons:
>
>I always have a CHB open on my TestCases. Being able to select a class and
>run it's tests (the CHB Class pane "Tests/Run" context menu command) is
>handy. I can also select an abstract class and the SUnitbrowser will open
>and run the subclasses tests. I find this more natural than opening the
>TestRunner and using the drop-down box to select the TestCase/TestSuite.

> Thanks for more feedback on how you use this thing. That's what I'm trying to
> understand: why people like it.  Comments within ...
>
> On Sun, 21 Apr 2002 08:56:00 +1000, "Steve Waring" <[hidden email]> wrote:
>
>
>>Hi Ron,
>>
>>
>>>It's interesting but I'm not sure just how it helps
>>>me moment to moment. Tell me a bit about how
>>>you use it?
>>
>>I have been using Jeffrey's SUnit Browser, and I do find it easier to use
>>for
>>the following reasons:
>>
>>I always have a CHB open on my TestCases. Being able to select a class and
>>run it's tests (the CHB Class pane "Tests/Run" context menu command) is
>>handy. I can also select an abstract class and the SUnitbrowser will open
>>and run the subclasses tests. I find this more natural than opening the
>>TestRunner and using the drop-down box to select the TestCase/TestSuite.
>
>
> I always have a TestRunner open. That's how I get my testing fix every two
> minutes. The Tests/Run might be useful. I think I might prefer that to hook to
> the TestRunner though. And as I mentioned, I don't like that it opens a new
> window every time I blink. (Ah, I see that sometimes it doesn't. Nicer than I
> had noticed ...)
>
>>I find it quicker to select and open a debugger on a failing or error test,
>>because the tests are listed rather than in a drop-down box.
>
>
> Yes. I'm not sure I'd use either of them that way. I don't need a list of all
> tests, I just need a list of failing tests.
>
>>I like being able to select a single test, and step into it or run it, as
>>well as debug it.
>
>
> Yes, that's very nice. I think I'd put it in the CHB if it were me ...
>
>>A typical use case for me is:
>> -Write a new test in my TestCase CHB.
>> -Run the TestCase's tests (right-click "Tests/Run"). This will open a
>>SUnitBrowser if it is not already open.
>> -Open a debugger on a failing/error test (right-click "Debug").
>> -Work.
>> -Select the single test that was the problem, and "Run" it again.
>
>
> I would always rerun them all. Takes essentially no more time and saves all that
> thinking and all that later saying "Damn".
>
>>I find that I can do this quicker and more easily in SUnitBrowser than I can
>>in the TestRunner. It may only save one or two mouse-clicks, but they add up
>>over time.
>
>
> Yes. When mouse time is what's really slowing me down I'll worry about that
> more. Right now it is thinking that slows me down. But I agree, things want to
> be right at the fingertips.
>
> For example, rightclick, drag, drag out isn't really the fastest way I think
> think of to run a test.
>
> I'll play with it a bit and see what I think, now that I have an idea of how
> people use it.
>
>>Thanks Jeffrey!
>
>
> Indeed ...
>
>>Steve Waring
>
>
> And thank you.
>
> Ronald E Jeffries
> http://www.XProgramming.com
> http://www.objectmentor.com
> I'm giving the best advice I have. You get to decide whether it's true for you.