coverage.
That’s very invasive to the code being instrumented, though. Hacking the
exemption out of Devel::Core seems like the far more robust alternative.
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
Hi Michael,
* Michael G Schwern [2012-04-13 04:00]:
> On 2012.4.11 1:01 PM, Aristotle Pagaltzis wrote:
> >>Unless I'm mistaken, Test::AutoBailOut is doing to need a global
> >>$SIG{__DIE__} handler or override CORE::require or add something to
> >>@INC or
thor can make each of these choices whichever way
they like, and so can Andy. Likewise with AutoBailout. The stop energy
he is throwing at it has no substantive reason so far, only “I don’t
care for this”.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
e, esp seeing
as it’s only a dozen lines of pure Perl.)
> But that's just me.
Yup. And it’s a free country. :-)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
Btw Ovid,
* Ovid [2012-04-11 19:10]:
> done_testing is applicable to every test module and solves the far
> more common issue of hating maintain a plan.
^^
a little Freudian slip there? :-)
terminal :)
That is not relevant to t/00-load.t though, nor applicable when BAIL_OUT
is involved, and here we are considering both of these.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Michael G Schwern [2012-04-11 20:10]:
> On 2012.4.11 9:53 AM, Aristotle Pagaltzis wrote:
> >I don’t see how it is any more magic than `done_testing`.
>
> done_testing() has no global side effects, it's just a function.
>
> Unless I'm mistaken, Test::AutoBailOut i
* Smylers [2012-04-11 18:20]:
> Aristotle Pagaltzis writes:
> > my $reason = 'Tests must succeeded';
>
> Grammar correction if anybody is going to publish this in a module:
> "succeed", rather than "succeeded".
Woops. Thanks.
> > Ah d
* Ovid [2012-04-11 19:10]:
> * Aristotle Pagaltzis [2012-04-11 18:55]:
> > I don’t see how it is any more magic than `done_testing`.
>
> Because done_testing is applicable to every test module and solves the
> far more common issue of hating maintain a plan. I would argue that
any case ever.
My suggestion to ship AutoBailOut was so you would be able to suggest it
as a replacement in the docs, as it covers the one case where `use_ok`
is even of interest (though still not the right solution).
But I guess you could do that even if it ships outside of Test::More.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
use Config;
use Test::Trap::Builder::TempFile;
use Test::Trap::Builder::SystemSafe;
use Test::Trap::Builder;
use Test::Trap;
use if $Config{'useperlio'}, 'Test::Trap::Builder::PerlIO';
no_bailout 'All prerequisites loaded';
Dead simple. H
deprecated too aggressively. However if it doesn’t make any
noise, then shedding it will never happen.
So maybe announce the deprecation during one perl release cycle and then
add a once-per-testsuite warning in the next?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
he two different kinds of reading, which on CPAN generally takes
the form of ::Manual PODs.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ser
fits right into its mission. More importantly,
use strict;
use warnings;
is hardly an experimental interface unproven by practice. :-)
Whereas new approaches to namespaces very definitely are.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
it, it will spread.
Modules are poor place for evangelism about unrelated conventions
in general, but I feel this especially strongly about Test::
modules with break-the-CPAN level adoption such as Test::Deep.
--
*AUTOLOAD=*_;sub _{s/::([^:]*)$/print$1,(",$\/"," ")[defined
w
leave
> the rest if it is really necessary.
“I made this so long only because I didn’t have the time to make
it shorter.” —Blaise Pascal
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
shell to it, so can
a pearl be. In fact a pearl in a shell is what iX magazine in
Germany has used as the masthead for their on-and-off Perl column
for at least a decade.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
archives/2007/01/12/sharecroppers
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
> as Test::NoWarnings).
END {
had_no_warnings();
all_done( 2 );
}
--
*AUTOLOAD=*_;sub _{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1}
&Just->another->Perl->hack;
#Aristotle Pagaltzis // <http://plasmasturm.org/>
* Michael G Schwern [2009-03-14 07:40]:
> Need to come up with a better way to deal with
> end-of-test-process tests.
Add a way in Test::Builder to register callbacks for specific
phases of the output and have TB API client code use that instead
of `BEGIN`/`END` et al.
Regards,
--
Ari
“I don’t care about backcompat” is
no way to go about designing a format that succeeds widely.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
way of doing it as a test numbering scheme? I would
still prefer that…
Although, that solution is acceptable as a distant second choice.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
antime,
people will want to be able to get the information back out of
their TAP streams before formal subplans become part of the
syntax. So worrying about how they will process the output of a
stream containing implicit subplans seems entirely appropriate.
Regards,
--
Aristotle Paga
* Michael G Schwern [2009-02-19 08:40]:
> it doesn't require any extra TAP reader logic to determine pass
> or fail.
I’m not talking about pass/fail, I’m talking about finding out
about subplans, from the consumer end.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Michael G Schwern [2009-02-19 06:35]:
> Aristotle Pagaltzis wrote:
> > But injecting artificial test results seems like a fairly big
> > modification to the format’s semantics to me, and I’m not
> > comfortable with the idea of doing that for no greater reason
>
* Michael G Schwern [2009-02-18 22:45]:
> Aristotle Pagaltzis wrote:
> > * Michael G Schwern [2009-02-18 21:55]:
> >> One of the issues with that approach is Test::Builder's
> >> history can't store test #2 twice. So history is lost.
> >
> > Sho
* Michael G Schwern [2009-02-18 21:55]:
> One of the issues with that approach is Test::Builder's history
> can't store test #2 twice. So history is lost.
Shouldn’t this be fixed?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
the first leg
of the test program did not complete (test 2 is missing) and the
second leg overshot (there’s an extra test 4). That TAP stream
expresses these things precisely with no artificial extra test
results injected.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* nadim khemir [2009-02-11 18:35]:
> TAP::DOM maybe.
++, in case it still matters. (Catching up to old mail.)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
tricks to
reduce the pain, such as this one:
http://perl-qa.hexten.net/wiki/index.php/TestFAQ#How_do_I_update_the_plan_as_I_go.3F
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
y been
> run. Which is how no_plan works.
The nice thing about data-driven tests is that in most cases the
test program can programmatically derive the number of tests from
the test data so it can set up a plan without the programmer
having to count.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
can’t and then
it’s not.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
first is there it’s always the number of tests to skip.
So the `skip($desc)` variant must go. However, `skip()` can stay,
it doesn’t cause problems.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
an interface here but it was
laden with environment variable thinking; since realising that
for the mistake it would be, I have not yet come up with a solid
new idea.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
to the mirror network’s bit-for-bit identity contract. I
would not want to see the latter change.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Michael G Schwern <[EMAIL PROTECTED]> [2008-09-29 16:35]:
> Aristotle Pagaltzis wrote:
> > * Michael G Schwern <[EMAIL PROTECTED]> [2008-09-29 14:50]:
> >> MakeMaker can set a minimum umask if it wants to play
> >> security nanny
> >
> > On Wi
* Michael G Schwern <[EMAIL PROTECTED]> [2008-09-29 14:50]:
> MakeMaker can set a minimum umask if it wants to play security
> nanny
On Windows?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
NU curiosity. No other tar
that I checked does have it.
Honestly, though, if you are using tar on Windows, I don’t know
why you would want any other default. Patching EU::MM is the
pragmatic approach, and we probably can’t avoid it, but I think
it is the wrong place to fix this, still.
roup/perl.cpan.testers/2008/09/msg2290906.html
Someone tell him that his Perl installation is broken.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
r for unplanned maintenance all of a sudden.
What I’m saying is that no matter how much you reduce
the surface area for exploits, it’s not a solution;
closing the hole in question is the solution.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Eric Wilhelm <[EMAIL PROTECTED]> [2008-09-23 06:35]:
> Don't run them as yourself either then!
I don’t like my module library disappearing *either*.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
he surface area of any exploits, it doesn’t make them
a non-issue. I would prefer my homedir not to vanish, thank you
very much.
(Note that I’m not saying that this issue is a bona-fide exploit.
I’m just saying that running CPAN as non-root is not a way to
close any hole.)
Regards,
--
Aris
--
*AUTOLOAD=*_;sub _{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1}
&Just->another->Perl->hack;
#Aristotle Pagaltzis // <http://plasmasturm.org/>
n't think they limit votes the way PM does
Everyone gets 30 upvotes and 5 separate downvotes per day. So
they don’t limit votes the way PM does, but they do limit votes.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
-)
* David Cantrell <[EMAIL PROTECTED]> [2008-09-12 00:50]:
> I spent far more time than I should have trying to work
> 'Liturgy' into it.
I thought of suggesting that, as a joke. Then I thought, nah.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Nicholas Clark <[EMAIL PROTECTED]> [2008-09-10 17:30]:
> Why should I add a dependency to correct code to placate the
> CPANTS game?
If you don’t care enough to add a dependency, why care at all?
:-)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
hat the
> module runs cleanly with warnings enabled and should receive
> the kwalitee point.
Problem is, the shebang line doesn’t actually *do* anything.
The correct solution (which also doesn’t require changes to
CPANTS) is called warnings::compat. Assuming you actually care
that much…
Regar
e 15× as many
distributions – literally more than half of the CPAN. This one
isn’t nearly as bad, even if it’s more than bad enough. Good
thing it’s a dev release, eh?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
of people who shut down
> needed works because they're personally inconvenienced.
OK, this just took a turn to the weird and now I’m lost. What did
you mean by your previous reply?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Aristotle Pagaltzis <[EMAIL PROTECTED]> [2008-09-09 09:05]:
> “I broke CPAN”
Btw, Michael, do you have a t-shirt that says that? Because if
not, we really need to make you one. :-)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
it’s not quite an
“I broke CPAN”-level problem, but it’s still significant.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
a waste not to exploit that.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
the list
wasn’t too huge, we could then prod all the authors by mail to
ask them to fix their crud, thus mostly averting the disruption
even before it happens.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
t I feed it match all the cases I want to exclude.
I tried variations on
use\s+Test::More.*no_plan\s*[')/]\s*[^;]
but that matches pretty much every `use Test::More` line with
`no_plan` on it ever written, regardless of what follows.
If anyone can see something that I can’t, please tell me.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
e use.perl journals (yes, that’s me).
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
and made part of the `distcheck` targets
of the various Perl distro toolchains.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
I just want to know if the code works or not. I
would be interested to know that you don’t care about supporting
my configuration, but as you don’t even care enough to declare
your non-support explicitly, I have to find out otherwise.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ng at
least two (did I count correctly?) substantial changes to how
CPAN::Reporter grades tests, in order to prevent particular
classes of bogus FAILs. Isn’t that a demonstration of exactly the
same care?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
not
extend to satisfying the users’ expectations according to *their*
understanding, then the users have a legitimate case for knowing
that your distributions are made of FAIL as far as they are
concerned. Whether you choose to care is then your prerogative,
obviously.
Regards,
--
Aristotle Paga
on
between the two is their confusingly similar naming. CPANTS tries
to lint-check your distribution and code without running any of
it; the CPAN Testers download your releases, install any prereqs
and then run your test suite. The goals and designs of the two
projects as well as their participants are entirely different.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
N::Reporter entirely if
> a Makefile.PL has been generated by CPAN.pm.
Sounds good. Presumably those distros are all so old that their
authors are unlikely to have an interest in test reports
generated almost a decade after release.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
be just a little more
robust? I’m not sure what that would entail, of course; what
*did* distributions of the time look like? There have to be more
cues in there than *just* the absence of a Makefile.PL, I hope?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
t believe anyone would think
this could ever *ever* work, though Andreas does not strike me as
the type to put harebrained heuristical magic in code. So I have
to wonder what the justification for this behaviour might be. Is
it really necessary or even helpful?
Regards,
--
Aristotle Pagaltzis
* Andy Lester <[EMAIL PROTECTED]> [2008-09-03 02:55]:
> On Sep 2, 2008, at 7:44 PM, Aristotle Pagaltzis wrote:
>> Seriously? First you say you want them to play in their own
>> sandbox, then you say they’ve never asked anyone?
>
> Yes, both of those are true.
Yes, taki
iving people yet another unrelated module to know
about (which they’ll only hear of if they follow an arbitrarily
chosen 3 out of 15 mailing lists) is not an improvement of the
situation.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
eople with possibly
contrary opinions or with extradisciplinary viewpoints is
ultimately a better strategy.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
email me and say "this broke our software!"
++
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
Testers arcana, so people wouldn’t have to stumble onto a
wiki page in the bottom of a locked cabinet stuck in a disused
lavatory with a sign on the door saying “beware the leopard”
in order to learn these trivia.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
implicity,
but precedes it.
So maybe there is hope.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
the
distribution as data (and the intent of installing it is even
less so), you need the exact list of prereqs.
META.yml is neither relevant nor useful for that.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
end for them to
be used, and doesn’t go out of its way to accomodate the potato
bag usage, fewer people will be tempted.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
erstand JSON and SHOULD understand
> YAML."
I could arrange myself with Schwern’s desire, so long as we could
agree to make that SHOULD a MAY. That would in fact work very
well for me.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
d files aren't of any use
> to day to day development.
No it doesn’t, each branch can keep a different list in
`.fooignore`.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
n. No?
I can’t currently think of any reason for which this would fail,
although I might be missing something obvious.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
one I’ve used
has a `status` command that tells me what I’ve touched, and in my
experience it is be much more reliable than `MANIFEST`. So is this
discussion in your workplace actually a tooling issue?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
deliberately not saying “release it”
since that would imply polishing it to a degree you probably have
no desire for.)
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* David E. Wheeler <[EMAIL PROTECTED]> [2008-08-18 19:25]:
> I don't believe it's possible to get that info in JS, is it?
Just seen: http://eriwen.com/javascript/js-stack-trace/
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
better
is when the contents of a data structure have to be
printed in skimmable form and the data structure shape
itself is not particularly important, only its contents.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ght up is not that the *working
group* needs to attend IETF meetings thrice yearly, but *the
chairman* of the WG does.
We’re talking about one person, the chair, not about the entire
working group.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ble of
serialising tricky data structures correctly. If you care about
those kinds of things, you probably want to use a language-specific
serialiser and put its output in the TAP diagnostic as a string.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
YAML::Tiny as our spec, it
> already has limitations that hit us at the BBC.
In what way, and why would that be relevant to TAP? Would JSON
not have those same limitations?
(It’s kinda funny that I’m finding myself the YAML’s advocate
now, considering how much I dislike it in general…)
Regards,
--
* Graham Barr <[EMAIL PROTECTED]> [2008-08-11 03:05]:
> On Aug 9, 2008, at 8:38 PM, Aristotle Pagaltzis wrote:
>> * Todd Rinaldo <[EMAIL PROTECTED]> [2008-08-10 03:35]:
>>> What alternatives do you recommend?
>>
>> See Tom Heady’s reply on this thread.
&g
* Todd Rinaldo <[EMAIL PROTECTED]> [2008-08-10 03:35]:
> What alternatives do you recommend?
See Tom Heady’s reply on this thread.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ated.
And whenever I tell people that FindBin is broken and they should
not use it, they look at me like I told them I’m seeing ghosts.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
or however many. And if you expect
reams of output, you open a fresh terminal for it. Problems
solved.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
es. Compared to a full RDBMS, SQLite is
an RDBM without the S – Drizzle is more of a… DMS. Essentially it
goes back to MySQL’s flatfile-with-quasi-SQL-frontend roots.
Whether they take off from there in any interesting direction
remains to be seen.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
). But that is hypothetical; reality
is that you don’t get even as far as that.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
validate the POD.
So please disregard that part; it is infeasible only to check POD
for good form (much less style), whereas it is entirely feasible
to check that the POD will be parsed correctly by practical POD
processors.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Eric Wilhelm <[EMAIL PROTECTED]> [2008-07-01 00:15]:
> # from Aristotle Pagaltzis
> # on Monday 30 June 2008 14:42:
>
>> But *even if* the line was difficult to find, it seems to that
>> just because we were unable to agree exactly where it is
>> doesn’t imply th
y can only be used for comparisons between modules if you
> open a new browser window/tab and manually lookup each one.
Disagree. Whether the module is packaged correctly has nothing
to do with its purpose and is a piece of information that stands
entirely on its own.
> All of it is potentially useful data to someone, but if it is
> going to be anything besides a game, it probably needs more
> ways to be queried.
Agree on that.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
metrics only. In that case I see it as a
useful social hack. The hall of fame as an indicator of “these
authors consistently take the necessary care to make sure you
won’t have problems with their software for no good reason” seems
fine to me, at least. The hall of shame is rather more debatable.
* Ovid <[EMAIL PROTECTED]> [2008-06-29 10:55]:
> --- On Sat, 28/6/08, Aristotle Pagaltzis <[EMAIL PROTECTED]> wrote:
>> I think the game is actually an excellent idea. The problem is
>> with the metrics. Here are some metrics that are inarguably
>> good:
>>
strings that are never tained.)
Thus it might be useful to see a page listing the distributions
whose modules do `use re 'taint';`, but it’s less than helpful
to rank module authors by how many of their modules do so.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
tely a common mistake that module authors can
> > easily fix.
>
> Perl::Critic?
Took the words out of my, well, fingers.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
ave since registered without any problems,
as David Wheeler just did, so I have no idea if your troubles are
related to mine.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
arose. Your pgTAP experiments would be a perfect
example of the sort of efforts we hope to see more of. As you
wrote, just a little tinkering and boom, you’re most of the way
to harnessing all the existing testing infrastructure (pun
intended); that’s the power of TAP.
Regards,
--
Aristotle P
Hi David,
I think you wanted to send this to [EMAIL PROTECTED]
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
edience
demands forgoing the extra work, however, then having a cheap,
suboptimal option to resort to is better than having to forgo
testing entirely.
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
* Michael G Schwern <[EMAIL PROTECTED]> [2008-05-18 05:30]:
> Aristotle Pagaltzis wrote:
>>> As a technique, paying attention to how broken code changes,
>>> why does it matter that broken code breaks differently? What
>>> does this information tell you that mig
1 - 100 of 132 matches
Mail list logo
