Andy,
I’ve accumulated a number of test functions in our work codebase for
doing what I call “expressive” tests to avoid common cut & paste. I’m
using the term “expressive” for now because they’re expressing what it
is you want, rather than making you write the code that explains them.
Sounds
> On Jun 24, 2016, at 12:57 PM, Buddy Burden wrote:
>
> What sort of methods did you have in mind? I might have something to
> contribute, if you would be interested in contributions.
I’ve accumulated a number of test functions in our work codebase for doing what
I call “expressive” tests t
Andy,
My ultimate goal here is to create a batch of convenience test methods ...
What sort of methods did you have in mind? I might have something to
contribute, if you would be interested in contributions.
-- Buddy
The pod for Test2.pm explains the namespaces. They are intended for all new
tools/plugins/events/etc. Test2::Xxx should be for extentions to the
framework. Test2::Tools::* and test2::Plugins etc are open to anyone.
On Jun 24, 2016 7:39 AM, "Andy Lester" wrote:
>
> On Jun 24, 2016, at 12:46 AM, Ch
> On Jun 24, 2016, at 12:46 AM, Chad Granum wrote:
>
> Is the intent that when people will create them as Test2::Tools::Whatever?
> Sort of like Perl::Critic::Policy::* is done? Or are we still staying as
> Test::Whatever?
What about naming? Test2::Tools::Whatever? Or do we see the Test2
