On Mar 19, 12:52 pm, "Edward K. Ream" <edream...@gmail.com> wrote:
> On Thu, Mar 19, 2009 at 2:50 AM, zpcspm <zpc...@gmail.com> wrote:
>
> > I'm using @test nodes for writing unit tests.
>
> > The headlines of my test nodes usually follow the '@test <class method
> > name>' pattern.
>
> I don't see the problem. If '@test join' is failing, and there are two
> '@test join' nodes, rename the nodes @test classA.join and @test
> classB.join. Then rerun the tests.
I agree, this is a workaround. I am still a bit intimidated by the
redundancy in the headlines:
- class MyClass
+ @test MyClass.get()
+ @test MyClass.do_something()
As you can see, the MyClass string is redundant. leo is nice because
it allows keeping data in a tree, so nested nodes are logically
related to the parent node and can borrow its properties. Your
suggestion solves my problem, but bothers a bit my aesthetic
perception of the data in a leo outline. Of course, I admit that this
can be qualified as zealotry :-) My goal is not to criticize, my goal
is to share my thoughts with the purpose to gain more experience
related to leo.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to leo-editor@googlegroups.com
To unsubscribe from this group, send email to
leo-editor+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
