Re: TPF Devel::Cover grant report April 2013

* Paul Johnson p...@pjcj.net [2013-05-01T16:40:17] In accordance with the terms of my grant from TPF this is the monthly report for my work on improving Devel::Cover covering April 2013. [...] This month I released Devel::Cover 1.02 but, apart from that, almost all of my work on Devel::Cover

Re: TPF Devel::Cover grant report May 2013

* Paul Johnson p...@pjcj.net [2013-06-23T18:43:41] In accordance with the terms of my grant from TPF this is the monthly report for my work on improving Devel::Cover covering May 2013. Thanks, Paul! Looks good. I look forward to putting some of this work to good use myself! -- rjbs

TAP::Harness and -w

I just submitted: https://github.com/Perl-Toolchain-Gang/Test-Harness/pull/16 ...to document two undocumented changes. First, the removal of turn on -w by default with no easy way to turn it off and secondly the reversion of that. These commits are, respectively:

Re: TAP::Harness and -w

* Leon Timmermans faw...@gmail.com [2013-07-04T14:04:21] By what process? Define consensus? Given Andy is the official maintainer and Ovid is the effective maintainer, I don't think they need our consensus a priori. 06perms.txt says: Test::Harness,ANDYA,m Test::Harness,MSCHWERN,c

Re: TAP::Harness and -w

* Eric Wilhelm enoba...@gmail.com [2013-07-04T17:33:45] # from Leon Timmermans on Thursday 04 July 2013: ewilhelm : We should keep the original change, but update EUMM to restore -w I'm not sure that's what he meant. Yeah no. I said get rid of Test::Harness. TAP::Harness provides a

Re: TPF Devel::Cover grant report June 2013

* Paul Johnson p...@pjcj.net [2013-08-31T18:59:11] In accordance with the terms of my grant from TPF this is the monthly report for my work on improving Devel::Cover covering June 2013. +1, thanks Paul. -- rjbs signature.asc Description: Digital signature

Re: TPF Devel::Cover grant report July 2013

* Paul Johnson p...@pjcj.net [2013-08-31T19:01:09] In accordance with the terms of my grant from TPF this is the monthly report for my work on improving Devel::Cover covering July 2013. +1, Thanks, Paul! The rest of the work this month was spent on p5cover. This is the project to get test

Re: TPF Devel::Cover grant report August 2013

* Paul Johnson p...@pjcj.net [2013-08-31T19:02:48] In accordance with the terms of my grant from TPF this is the monthly report for my work on improving Devel::Cover covering August 2013. +1, thanks, Paul! 5.18.1 breaks Devel::Cover. I'm very sorry to have been part of the problem, here.

Re: TPF Devel::Cover grant report July 2013

* Paul Johnson p...@pjcj.net [2013-09-02T06:37:20] And I'm not really sure what a 50¢ explanation is, so I hope I've guessed correctly. Perfect, thanks! -- rjbs signature.asc Description: Digital signature

Re: TAP::Harness and -w

* Ovid curtis_ovid_...@yahoo.com [2013-09-18T04:19:28] As I said in my previous email on July 7th: backwards-incompatible changes to the backwards-compatibility layer (Test::Harness) are not a good idea. The proper response is to have people impacted by this issue switch to TAP::Harness, as

Re: TAP::Harness and -w

* Leon Timmermans faw...@gmail.com [2013-09-18T19:21:44] Or both just setting $Test::Harness::switches = ''… Yes. I was cleaning out ~/tmp on the flight over here and I found this dzil plugin: package inc::STFUEUMM; use Moose; extends 'Dist::Zilla::Plugin::MakeMaker'; use

Re: TAP::Harness and -w

* Leon Timmermans faw...@gmail.com [2013-09-17T11:26:40] Just as I expected, make it a wiki means it gets warnocked again. Can we please make a decision, or if we must first come to an agreement on how to make it? Allow me to offer this:

Test-Simple 0.98_06

Test-Simple has built up a nice set of changes in the two years since its last release. Some of these are adjustments to changes in core for which Test-Simple was patched in blead. Test-Simple 0.98_06 integrates (or replaces) those fixes, and has other fixes of its own. Please test your code

Test::Simple 1.0!!! (plus 0.001001001)

NOW WITH MORE DIGITS! We released 0.99 recently. There was a regression. We need a new release. To sync up with the 1.005001 versioning, we are moving to X.YYYZZZ-style. I think the longer-term goal will be to use Perlified semantic versions. For now, I'm just dealing with important

Test-Class 0.40

Once Test::Simple 1.001002 is release, I will upload Test-Class 0.40, which makes it pass its tests with 0.98 and previous as well as 1.001001 and later. 0.99 is broken. You can test it here: https://dl.dropboxusercontent.com/u/88746/perl/Test-Class-0.40.tar.gz -- rjbs signature.asc

Re: Discussion/request on Test::More , have it add t/lib to @INC if -d

* Torbjørn Lindahl torbjorn.lind...@gmail.com [2014-01-30T19:59:04] It seems t/lib is a common place to put modules used to support testing, how about having Test::More push that path to @INC if -d 't/lib' ? It would I suggest this alternative: use t::lib::MyPackage; ;) -- rjbs

Re: Discussion/request on Test::More , have it add t/lib to @INC if -d

* Eirik Berg Hanssen eirik-berg.hans...@allverden.no [2014-01-31T10:17:53] Yeah; just name the package accordingly, and, screwy or not, it'll still work: package t::lib::MyPackage; sub import { print import() was called\n } This is my advice as well as my custom. -- rjbs

Re: TPF Devel::Cover grant report April 2014

* Paul Johnson p...@pjcj.net [2014-05-20T17:50:35] In accordance with the terms of my grant from TPF this is the monthly report for my work on improving Devel::Cover covering April 2014. Thanks, Paul, +1. -- rjbs signature.asc Description: Digital signature

Re: anyone want to adopt Test::Tester?

* David Cantrell da...@cantrell.org.uk [2014-06-26T09:19:00] I understand that Test::Builder::Tester is the way to go these days - and it's distributed with Test::Builder, so incompatibilities should never* happen. Test::Tester is really nice and easy to use. Test::Builder::Tester is awful

Re: TPF Devel::Cover grant report May/June 2014

* Paul Johnson p...@pjcj.net [2014-07-20T18:59:51] Hours worked: Total 25:00 Thanks, Paul, +1! -- rjbs signature.asc Description: Digital signature

Re: new Stream Test::Simple question, XS requirement

* bulk88 bul...@hotmail.com [2015-04-25T17:57:19] Since Test::Stream::Context's core design uses weaken() everywhere, that means new Test::Simple always requires XS building (for Scalar::Util), which means it will never run on miniperl, and hence, new Test::Simple will never be in Perl core,

Re: new Stream Test::Simple question, XS requirement

* bulk88 bul...@hotmail.com [2015-04-25T23:56:23] Because of the rjbs post that supposedly (someone else should confirm this) minitest does not use Test::*, new Test::Simple can use all the XS it wants. Re-confirmation welcome! For the record: My first check was scanning all the tests run by

Re: Test-Stream! Test-Simple! Go!

* Ricardo Signes <perl...@rjbs.manxome.org> [2015-11-23T18:12:22] > * make a set of GitHub issues for the punch list, tagged as such https://github.com/Test-More/test-more/issues?q=is%3Aopen+is%3Aissue+label%3ATest-Stream > * make GitHub issues for other topics to review, also

Test-Stream! Test-Simple! Go!

Wow, the last update on this was in April! Then stuff came up. Has all the stuff that came up gone down? I hope so. I think that there is not one person who wants the up-in-the-air-ness of Test-Builder-on-Test-Stream to last longer than it has to. I sure don't. Now that it seems like there

Re: Test2/Test::Builder release plan

* Chad Granum [2016-03-19T13:03:34] > RJBS and I have spoken, and feel it is time to set a release date for > Test2/Test-Builder. We have agreed that doing it at the QAH in Rugby is a > good time. The plan is to release Test2 and the new Test::Builder as stable > either at the

Re: Test::Buildder v. Test2 subtests

* Chad Granum [2016-12-13T11:13:56] > I would like to see the results when you use > Test2::Tools::Subtest::subtest_streamed() which is the actual equivalent to > Test::More::subtest(). Thanks for the pointer. I have tried this and got identical ("bad") results to

Test::Buildder v. Test2 subtests

I've hit a nasty (to me) difference between Test2::API::run_subtest and Test::Builder::subtest. Shout out to Matthew Horsfall for helping localize the problem. Here's my trivial reproducer: #!perl use strict; use warnings; use Test::More; use Test2::API; my $code = sub { if

test/subtest flow control with exceptions

Often, I have a test like this: subtest "do things with an api" => sub { my $result = $api_client->do_first_thing; is( $result->documents->first->title, "The Best Thing", ); ... }; Sometimes, the result comes back with zero documents. ->first throws an

Re: test/subtest flow control with exceptions

* Chad Granum [2016-11-30T10:30:38] > I do have implementation commentary however: Thanks, greatly appreciated! > * You should not be obtaining a context inside your subtest (specifically > line 18 So, I've moved it to after the eval. I (think that I) need it inside the

Re: Test::Buildder v. Test2 subtests

* Chad Granum [2016-12-13T11:35:19] > ok, thanks for trying that, I will look into it when I have time and if > nothing else at least explain why it behaves like it does. If it is a bug I > will fix it. This has remained a problem for me, so this morning I had a run through

Test-Deep as_test_deep_cmp branch

I've filed a PR against Test-Deep: https://github.com/rjbs/Test-Deep/pull/52 addresses https://github.com/rjbs/Test-Deep/issues/50 The idea is: When you call cmp_deeply($have, $want), objects found in $want are either Test::Deep::Cmp objects or not. If they are, they do their special

Re: Test-Deep as_test_deep_cmp branch

* Ricardo Signes <perl...@rjbs.manxome.org> [2016-12-18T09:08:23] > When you call cmp_deeply($have, $want), objects found in $want are either > Test::Deep::Cmp objects or not. If they are, they do their special test > magic. If they are not, they are more or less compared to th

Re: Updated CPAN River available

* James E Keenan [2017-04-12T22:15:22] > For me the most interesting aspect of this fifth round is that 29 > distributions which appeared in order-of-battle-20170409.txt (the > previous round focusing on no-dot) no longer appear in > order-of-battle-20170412.txt. That is,

<    1   2