NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
My hackathon plans (Score:1)
Nested TAP would be good, I think. I'm planning on getting Test::Class::Sugar to a releaseable point over the weekend, and hopefully making a good start on something like cucumber http://cukes.info/ [cukes.info] with Devel::Declare driven syntax, though I might get sidetracked into trying to write a perlish autotest if such a thing doesn't already exist.
Both those (and definitely the cucumber port) would benefit from nestability.
I'm not sure when I'm going to get there - won't be there 'til Saturday morning.
My hackathon plans (Score:1)
.. Another vote for nested TAP here for obvious reasons!
Me, I hope to fix some of the more broken bits of the T::C internals, make whatever changes Piers needs for T::C::Sugar, and knock a few of the things off the T::C to do list.
Along with anything else that seems useful :)
I'm also going to annoy Curtis with a long conversation about TDD. Especially if I get around to finishing up the blog post(s) that have been sitting on my desktop for the last week :-)
Re: (Score:1)
(Also - I want to get Curtis to educate me about Role based design... but that's not QA related)
Re: (Score:2)
Bring me some sample code which abuses inheritance (multiple inheritance and several levels of inheritance are good), and I can help you refactor it. You'll be amazed at what RO (Role Oriented) Programming can do.
Or if there's something tractable on the CPAN, I could play with that.
agreements (Score:1)
Nested TAP++
TAP Diagnostics ++
Also, I was planning on finally getting some time to give Smolder some love. I've got a list of features from the Parrot developers and am also in the middle of a rewrite to ditch apache and use a Perl HTTP server and make it CPAN installable.