On Fri, Aug 19, 2011 at 3:23 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
Before leading a revolution, we can maybe have this work for unit test first :-)

Actually, when I think about it, having not the setUp visible when writing tests make the setUp functionality mostly useless.


Also, I usually write the setUp to remove duplication, so often after the second test method. A refactoring "extract to setUp" would be cool too.

Another point, when I have a hierarchy of TestCase I often feel I need a "merged setUp view"��

Laurent.

��

Cheers,
Alexandre


On 19 Aug 2011, at 15:19, laurent laffont wrote:

> On Fri, Aug 19, 2011 at 3:09 PM, Alexandre Bergel <alexandre.bergel@me.com> wrote:
> Hi!
>
> I know there are many TDD shoguns around.
>
> I was wondering whether I am the only one suffering from the need to see the definition of setUp before writing a test method. Unfortunately, current tool does not automatically show the definition of setUp when I want to write a new test.
> The cost of seeing how the setUp is done is high: need to open a new window, clicking to restore the context on the first window, ...
>
> Am I the only one?
>
>
> No. I would like too.
>
> But not only for tests. I often need to look at several related methods at once while developing.
>
> Laurent.
>
>
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel ��http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel ��http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.