On Mon, 2004-02-02 at 15:46, Adrian Howard wrote:[snip]
I'd rather print less if I don't really care what the name is, though I[snip]
don't feel exceedingly strongly that way. It just seems that a default
test name is there only to have a test name, not because it provides any
useful information.
People should use test names if they make the tests easier to understand
and to maintain, not because people should use test names.
Oh I agree :-) I just want to define my test name elsewhere so rather than having duplication:
define correct_answer : Test { is $answer, 42, 'correct_answer' };
or meaningless method names:
define test123 : Test { is $answer, 42, 'correct_answer' };
I can have the (in my eyes) neater:
define correct_answer : Test { is $answer, 42 };
I like meaningful method names in Test::Class test suites, since I can use them to make quick-n-dirty documentation an AgileDox style <http://joe.truemesh.com/blog/archives/agile/000047.html>.
I was just wondering if there were any other use cases out there that would justify adding something more generic.
Adrian