Is there a doc somewhere that explains how to write one's own test module atop
Test2? I haven't found it if there is.
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?
Do we hav
Right now the Test2::API docs are probably all that is done. But my Test2
manual grant covers the document you request as one of the 2 primary goals.
I have plans for it, and will be getting to it just as soon as I settle
back in from YAPC.
On Jun 23, 2016 7:52 PM, "Andy Lester" wrote:
Is there a
> 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
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
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
> 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,
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 4:41 PM, Buddy Burden wrote:
>
>is_true($val);
>is_false($val);
>
> Because with just `ok($val)` you can tell whether it's true or false, but,
> when it inevitably fails, you really want to know what the bad value turned
> out to be.
I have a bool_eq() so you c
On Mon, Jun 27, 2016 at 4:34 PM, Andy Lester wrote:
>
> On Jun 24, 2016, at 4:41 PM, Buddy Burden wrote:
>
>is_true($val);
>is_false($val);
>
> Because with just `ok($val)` you can tell whether it's true or false, but,
> when it inevitably fails, you really want to know what the bad valu
Andy,
I don’t like the name bool_eq() (“booleans are equal”) but it was the
best I could come up with.
I still like `is_true` and `is_false`. :-)
-- Buddy
10 matches
Mail list logo