Christopher H. Laco wrote:
chromatic wrote:
On Tuesday 02 September 2008 11:01:44 David Golden wrote:
You encourage what you measure,
In theory, yes. In practice, that hasn't been the experience to date.
Testers over 70K:
1 587018 Chris Williams (BINGOS)
2 318527 Andreas J. König
David Golden wrote:
On Tue, Sep 2, 2008 at 2:23 PM, Christopher H. Laco [EMAIL PROTECTED] wrote:
Yes, the second one does error in the middle of the output...barely.
Had the errors been after the 50k, the report would be doubly useless:
[Output truncated after 50K]
does no good when
Aristotle Pagaltzis wrote:
* Ovid [EMAIL PROTECTED] [2008-09-02 22:40]:
For all of the bogus reports I get, I'd rather get the bogus
ones along with the good ones than nothing at all. I'd much
prefer that I find out immediately if there's a disaster rather
than have someone email me and say
Andy Lester wrote:
On Aug 21, 2008, at 4:36 AM, Ovid wrote:
Why? If we want other extensions, stripping them is probably bad.
We definitely want other extensions. I have a pending project that
relies on running .t and .phpt next to each other.
xoa
I've got one at home now that
Ovid wrote:
--- Sam Vilain [EMAIL PROTECTED] wrote:
However I
am yet to see anything other than a monkeypatch on Ovid's journal,
and an incomplete patch linked earlier on the thread.
Care to explain the term 'monkeypatch'?
I've always heard of it as injecting code into someone elses
A. Pagaltzis wrote:
* David Golden [EMAIL PROTECTED] [2007-12-19 17:30]:
It looks like it does (as long as you remove the -T from the
shebang in 01.real.t.
Anyone with Windows who cares to, please bang on
http://plasmasturm.org/attic/Proc-Fork-0.5.tar.gz
before I send it to the CPAN.
Matisse Enzer wrote:
I was following the comments in http://use.perl.org/~Alias/journal/34680
and came across something that was new to me, and seemed worthy of
repeating here - if only one other person learns this it'll be worth it:
In comment
chromatic wrote:
On Thursday 16 August 2007 20:14:31 Eric Wilhelm wrote:
I am certain that more than one 'extra tests' directory is needed, thus
the thought to make them into subdirectories (objections?)
(They cannot live under 't/' due to compatibility issues.)
Which compatibility
chromatic wrote:
On Friday 17 August 2007 09:31:50 Christopher H. Laco wrote:
chromatic wrote:
I've used t/author/ for quite a while without any compatibility issues.
Right, accept when your t/author tests are tests for you, the author and
my t/author tests are for my Author class
Adriano Ferreira wrote:
On 8/17/07, Christopher H. Laco [EMAIL PROTECTED] wrote:
chromatic wrote:
On Thursday 16 August 2007 20:14:31 Eric Wilhelm wrote:
I am certain that more than one 'extra tests' directory is needed, thus
the thought to make them into subdirectories (objections
chromatic wrote:
On Friday 17 August 2007 11:17:10 Christopher H. Laco wrote:
To whit: Who knows better whether foo.t is an author test or not [in the
absence of the actual human author]... The harness, or foo.t?
The author.
The harness asking the t files will always be more accurate
Adriano Ferreira wrote:
On 8/2/07, David Golden [EMAIL PROTECTED] wrote:
Having an actual pod/pod-coverage.t gives a handy place to put those
customizations. Yes, some of that could be put in
pod_coverage_options in a config or a ACTION_testpod method, but to
me, that introduces extra
Andrew Ford wrote:
I have corresponded with Ian Langworth and he has agreed that I should
revise the Perl Testing quick reference. I shall be converting it to
LaTeX and expanding it to be a two-sided card, which implies doubling
the amount of information on the card. I intend to publish it
chromatic wrote:
On Tuesday 31 July 2007 12:35:06 David Golden wrote:
On 7/31/07, chromatic [EMAIL PROTECTED] wrote:
1) POD can possibly behave any differently on my machine versus anyone
else's machine, being non-executed text and not executed code
What version of Pod::Simple do you
Eric Wilhelm wrote:
# from David Golden
# on Monday 30 July 2007 05:34 am:
The issue at hand is really *release* testing (i.e. did I bump the
version, did I test my Pod, do I use good style, etc.) being mixed
with *functional* testing -- and the corresponding push for release
testing
Eric Wilhelm wrote:
# from Christopher H. Laco
# on Monday 30 July 2007 11:14 am:
I don't agree. What runs when I do 'make test' is up to me, and if I
want to litter it up with 'author' tests, then that's my business;
right or wrong. Don't like it, then don't use my modules. (I still
think
Eric Wilhelm wrote:
# from Christopher H. Laco
# on Monday 30 July 2007 11:14 am:
I don't agree. What runs when I do 'make test' is up to me, and if I
want to litter it up with 'author' tests, then that's my business;
right or wrong. Don't like it, then don't use my modules. (I still
think
Adam Kennedy wrote:
For background on this email, see the following entry in my journal.
http://use.perl.org/~Alias/journal/33893
Lately, I've noticed a series of modules that are cargo-culting the use
of test_pod and test_pod_coverage in their tests.
Not only are we seeing spurious
Paul Beckingham wrote:
I'm wanting sparse output:
1..100 sparse
12 not ok
83 not ok
Which is three lines of output, instead of 97, but contains the same
information as:
1..100
1 ok
2 ok
...
12 not ok
...
83 not ok
84 ok
...
Thomas Klausner wrote:
Hi!
On Tue, Mar 06, 2007 at 02:34:16PM +, Andy Armstrong wrote:
Does anyone apart from Thomas Klausner know anything about the status
of CPANTS? It's been down for about five days now.
I'm trying to offer him free hosting for it but he doesn't seem to be
Thomas Klausner wrote:
Hi!
On Tue, Mar 06, 2007 at 10:01:09AM -0500, Christopher H. Laco wrote:
It's the CPANTS shuffle! Isn't this like, server/host 3 or so? :-)
It is, which is my punishment for beeing to lazy to set up my own
server :-)
No, lazy is good. Don't let anyone fool
chromatic wrote:
On Saturday 03 March 2007 18:18, Andy Lester wrote:
Good Lord do I get frustrated at the handwringing over test
counting. Look, it's simple. You write your tests. You run it
through prove. You see how many tests it reports. You add it at the
top of the file.
Yuval Kogman wrote:
On Sun, Feb 25, 2007 at 22:34:15 -0800, chromatic wrote:
Why not, I already have half of the other stuff in UNIVERSAL
Just don't tell Adam.
Or me. I have a personal hate relationship with MockObject in this way.
I love MockObject. I hate getting warnings about 3
Nik Clayton wrote:
Paul Johnson wrote:
On Thu, Feb 08, 2007 at 09:26:01AM +, Nik Clayton wrote:
[ I vaguely recall a discussion about this, but my search-fu is weak,
and I can't find it ]
Is there a standard way/idiom to get ExtUtils::MakeMaker to support
tests in subdirectories of t/?
Christopher H. Laco wrote:
While strolling through PlanetMVC, I noticed a free chapter about unit
testing using it's own testing library call Lime. Low and behold, my
eyes see TAP and some props to Test::More. Kewl. :-)
http://www.symfony-project.com/weblog/2007/01/17/book-preview-read
Chris Dolan wrote:
On Nov 7, 2006, at 6:15 PM, Christopher H. Laco wrote:
I just wanted to get some thoughts on this before I filed a bug report
with either PPI or Perl::Critic:
I'm going through and testing all of my *.t files for RequireTestLabels.
I was humming right along when I ran
I just wanted to get some thoughts on this before I filed a bug report
with either PPI or Perl::Critic:
I'm going through and testing all of my *.t files for RequireTestLabels.
I was humming right along when I ran into an oddity. The newest
Perl::Critic 0.21 + PPI 1.118 complains that the tests
Anyone have any ideas on this blip?
http://handelframework.com/coverage/blib-lib-Handel-Base-pm.html
line #171
Lord knows, it doesn't really matter since that's the only piece left,
but I'm kinda of curious. This is under Devel::Cover 0.59 under 5.8.4,
5.8.6, and 5.8.8
-=Chris
Chris Dolan wrote:
On Nov 2, 2006, at 11:01 PM, Thomas Klausner wrote:
metayml_conforms_spec currently very much busts the CPANTS game. I'm
checking if the files comply to META.yml spec 1.2. Most don't, because
they seem to use 1.0
Should I switch to 1.0-checking?
No. The CPANTS game is
Christopher H. Laco wrote:
Thomas Klausner wrote:
Hi!
I had some time recently and added some first META.yml checking to
CPANTS (with the help of Gabor Szabo):
metayml_is_parsable
metayml_has_license
metayml_conforms_spec
metayml_has_license now indictes whether there's a computer
Christopher H. Laco wrote:
Chris Dolan wrote:
On Nov 2, 2006, at 11:01 PM, Thomas Klausner wrote:
metayml_conforms_spec currently very much busts the CPANTS game. I'm
checking if the files comply to META.yml spec 1.2. Most don't, because
they seem to use 1.0
Should I switch to 1.0-checking
Thomas Klausner wrote:
Hi!
I had some time recently and added some first META.yml checking to
CPANTS (with the help of Gabor Szabo):
metayml_is_parsable
metayml_has_license
metayml_conforms_spec
metayml_has_license now indictes whether there's a computer readable
license in META.yml,
Chris Dolan wrote:
On Nov 2, 2006, at 11:01 PM, Thomas Klausner wrote:
metayml_conforms_spec currently very much busts the CPANTS game. I'm
checking if the files comply to META.yml spec 1.2. Most don't, because
they seem to use 1.0
Should I switch to 1.0-checking?
No. The CPANTS game is
Michael G Schwern wrote:
Christopher H. Laco wrote:
Files that declare: --- #YAML:1.0 should pass the 1.0 spec
Files that declare: --- #YAML:1.1 should pass the 1.2 spec
err...
Files that declare: --- #YAML:1.2 should pass the 1.2 spec
I know what I meant. :-)
I thought
Thomas Klausner wrote:
Hi!
I had some time recently and added some first META.yml checking to
CPANTS (with the help of Gabor Szabo):
metayml_is_parsable
metayml_has_license
metayml_conforms_spec
metayml_has_license now indictes whether there's a computer readable
license in META.yml,
Nicholas Clark wrote:
On Tue, Oct 24, 2006 at 08:08:45PM -0400, Christopher H. Laco wrote:
With most modules, I agree. But with utility modules like
Module::Pluggable, File::Find::Recursive, etc, not working under taint
I'd be surprised if the author of Module::Pluggable wasn't open
Paul Beckingham wrote:
I'm with Adrian. Printing out ok 100,000 times shouldn't be a
big deal unless you're reading the TAP via some sort of IP over
clay tablets protocol. But...
My test estimate is two orders of magnitude larger, so it actually is a
big deal to capture and store those
Michael G Schwern wrote:
Christopher H. Laco wrote:
I'm in the same boat. Recently, I've started testing my environment when
things go wrong. (I blame Andy). I have one test alone that has a test
count of 500,000+. That's a lot of oks to be processed, when I only want
the ones that didn't
Michael G Schwern wrote:
Christopher H. Laco wrote:
Shouldn't all tests be set to use tainting?
And by extension, shouldn't all modules run under -T?
(Just curious)
That would be nice, but tainting is a pain in the ass and not something I'd
be willing to universally inflict on all module
Jonathan Rockway wrote:
True. On the flip side, there's nothing more irritating that flipping
PerlTaintCheck On only to find out a crapload of modules don't run under
taint. And that's assuming you have control over whether the flag is set
of not. :-/
Maybe an example would help me
Adam Kennedy wrote:
WORKSFORME on Strawberry alpha 2.
I'm betting it's something to do with the -T, because the only
difference I can think of is that the build is running inside some sort
of alternative harness that does something differently...
Out of curiosity, why are your tests set
I'm having a idiot moment...
I'm trying to mock out some config reading tests for reading from
MP1/MP2 even though I don't have either installed. so I thought
Test::MockObjext is the answer!.
The following code goes boom with a 'Can't locate object method request
via package Apache':
use
chromatic wrote:
On Thursday 05 October 2006 12:25, Christopher H. Laco wrote:
I'm having a idiot moment...
I'm trying to mock out some config reading tests for reading from
MP1/MP2 even though I don't have either installed. so I thought
Test::MockObjext is the answer!.
The following
chromatic wrote:
On Thursday 05 October 2006 12:25, Christopher H. Laco wrote:
I'm having a idiot moment...
I'm trying to mock out some config reading tests for reading from
MP1/MP2 even though I don't have either installed. so I thought
Test::MockObjext is the answer!.
The following
Ovid wrote:
--- Ivan Tubert-Brohman [EMAIL PROTECTED] wrote:
Have you tried Pod::Spell and Test::Spelling? I think they already do
that.
I've tried Test::Spelling only to discover that there are so many
exceptions which it doesn't recognize that it was very painful to try
and include in a
Ovid wrote:
[snip]
It would be nice if I could just write 'use My::Test::More' in my test
scripts and have that provide what I need, but I'm not sure if trying to
re-export all of the test functions from Test::More (kind of like subclassing
which isn't a class) is a bright idea, but it's
Ovid wrote:
From: Christopher H. Laco [EMAIL PROTECTED]
I'm thinking about doing the same thing. Before Chris Dolan wrote a
Testing::RequireTestLabels policy for me (thanks!), I was going to
subclass Test::More and expose the usual methods and tack on my argument
checking.
Just threw
Chris Dolan wrote:
On Sep 24, 2006, at 5:42 PM, Christopher H. Laco wrote:
Ok, I'll play your game. :-)
http://perlcritic.tigris.org/svn/perlcritic/trunk/Perl-Critic/lib/Perl/Critic/Policy/Testing/
[Assuming I'm not silly] Empty! Rev. 667
-=Chris
D'oh! SVN commits work better
While trying to install the latest PPI from svn, I noticed that running
'dmake test' passed, and 'prove -b t/' failed.
As more and more people use Module::Install, it seems more and more
transient build/test related modules are being stuffed in the inc/
directory.
Given the talk about installers
Chris Dolan wrote:
On Sep 24, 2006, at 5:42 PM, Christopher H. Laco wrote:
Ok, I'll play your game. :-)
http://perlcritic.tigris.org/svn/perlcritic/trunk/Perl-Critic/lib/Perl/Critic/Policy/Testing/
[Assuming I'm not silly] Empty! Rev. 667
-=Chris
D'oh! SVN commits work better
I've got a crap loads of tests in Handel at the moment; 1+
checkpoints, and enough files that I hit the dreaded command line too
long under win32 [now fixed]. That's not saying all the tests are
glorious and not repetitive. :-)
I've still got a ways to go before I'm happy without the dist
Chris Dolan wrote:
[snip]
Done. I created Perl::Critic::Policy::Testing::RequireTestLabels and
added it to the Perl::Critic SVN at
http://perlcritic.tigris.org/svn/perlcritic/trunk/Perl-Critic
(username: guest, password: )
It was pretty simple to write. Below are the important bits of
A. Pagaltzis wrote:
* Chris Dolan [EMAIL PROTECTED] [2006-02-02 16:55]:
On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
I really like this idea. But as you pointed out, it's not just
authors that need to worry about running these tests, it's
packagers (ppm/deb/etc), automated testers
Andy Lester wrote:
On Fri, Dec 02, 2005 at 12:10:24PM -0800, Ovid ([EMAIL PROTECTED]) wrote:
I've wondered about this myself. I've taken over Class::Trait but I
can't take ownership of the RT requests.
RT should do it automagically. Email Jesse directly if not.
xoxo,
Andy
For which,
Andy Lester wrote:
On Fri, Dec 02, 2005 at 12:10:24PM -0800, Ovid ([EMAIL PROTECTED]) wrote:
I've wondered about this myself. I've taken over Class::Trait but I
can't take ownership of the RT requests.
RT should do it automagically. Email Jesse directly if not.
xoxo,
Andy
Which
Ovid wrote:
Hi all,
I've noticed that http://search.cpan.org/~ovid/HOP-Parser-0.01/,
amongst other modules, has no CPAN test results appearing even though
CPAN tester reports are coming in. I've seen this for other modules,
too.
Is there an announced reason for this I missed or is
Ovid wrote:
The code is designed well enough that adding new features is quick and
easy. Unfortunately, whenever I need to change my code I fire up a Web
server and view the results in the browser and then write the tests
after I've written the code (this is closely related to When
Adam Kennedy wrote:
Rather than do any additional exploding, I'd like to propose the
additional kwalitee test has_changes. I've noticed that a percentage
(5-10%) of dists don't have a changes file, so it can be hard to know
whether it's worth upgrading, or more importantly which version to add
Andy Lester wrote:
Usually, Test::* modules are only used for the test phase.
I really don't understand the idea of only used for the test phase,
as if the tests don't matter, or if there are levels of failure.
Either they install OK on the target system, and you can use them with
Andy Lester wrote:
On Tue, Sep 06, 2005 at 09:12:43AM -0400, Christopher H. Laco ([EMAIL
PROTECTED]) wrote:
If it serves no purpose for you, ignore it and go on
with life; as apposed to spending email list cycles on a
CPANTS-is-bad-why-are-we-doing-this diatribe.
It's not as simple
Kevin Scaldeferri wrote:
On Jun 3, 2005, at 1:40 PM, Paul Johnson wrote:
Certainly. Of course, it's always possible and quite likely that there
is a bug in my code somewhere. But there is also a chance that I am
conflating two ops, since I have yet to come up with a way to uniquely
identify
Tony Bowden wrote:
On Thu, Apr 07, 2005 at 08:56:26AM -0400, Christopher H. Laco wrote:
I would go as for to say that checking the authors development
intentions via checks like Test::Pod::Coverage, Test::Strict,
Test::Distribution, etc is just as important, if not more, than just
checkong
Tony Bowden wrote:
On Thu, Apr 07, 2005 at 12:32:31PM -0400, Christopher H. Laco wrote:
CPANTS can't check that for me, as I don't ship those tests.
They're part of my development environment, not part of my release tree.
That is true. But if you don't ship them, how do I know you bothered
David Wheeler wrote:
Greetings fellow Perlers,
I'm pleased to announce the first alpha release of my port of
TestSimple/More/Builder to JavaScript. You can download it from:
http://www.justatheory.com/downloads/TestBuilder-0.01.tar.gz
Very cool. Very sick. :-)
OK, now whos gonna build
Ken Williams wrote:
Since the 'build', 'test', and 'install' actions are considered the
critical path for installing a module, I think it makes sense to warn
(not die) during perl Build.PL when one of their
required/recommended/conflict dependencies aren't met. Thereafter, only
die/warn when
Michael G Schwern wrote:
[snip]
Sticking with ExtUtils::MakeMaker. :-)
[But where's the fun in that.]
I know you're joking, but you've flipped my rant switch.
I was. But at some level, I'm not.
If after changing one dist to use M::B I have more issues than I started
with [which was just checking
Michael G Schwern wrote:
On Mon, Mar 28, 2005 at 08:42:50AM -0500, Christopher H. Laco wrote:
That's another gripe of mine about M::B and create_makefile_pl.
It puts the requires AND build_requires in the PREREQ_PM in the
Makefile.PL, which I won't want; nor do I think it right for everyone
Randy W. Sims wrote:
There is my unpublished CPAN::Metadata at:
svn co http://svn.versiondude.net/randys/CPAN-Metadata/trunk/ CPAN-Metadata
It reads, writes, and validates metadata according to the spec. It still
needs a bit of work, and updates to the actual spec need to be
formalized before it
Michael G Schwern wrote:
On Sun, Mar 27, 2005 at 08:32:59PM -0500, Christopher H. Laco wrote:
Along the lines of converting to Module::Build...it went well until I
started doing tests...things that worked now break, probably do to how
they're now run...
t\xsp.Use of uninitialized
Is anyone aware of any existing code (aside from YAML) for grocking
META.yml?
I've got an itch. Aside from user side software tests, I'm also somewhat
addicted to developer tests (Test::Strict, Test::Pod, etc) to make sure
I'm not making stupid typo mistakes every time I upload a new version
Andy Lester wrote:
On Mar 26, 2005, at 6:29 PM, Christopher H. Laco wrote:
Is anyone aware of any existing code (aside from YAML) for grocking
META.yml?
Why are you changing it manually?
Well, unless I missed something [likely], to add things after the module
is created or updated. Changing
Christopher H. Laco wrote:
Michael G Schwern wrote:
On Sat, Mar 26, 2005 at 07:52:45PM -0500, Christopher H. Laco wrote:
Well, unless I missed something [likely], to add things after the
module is created or updated. Changing requirements, recommends, and
build_requires for starters. Sometimes
David Wheeler wrote:
Hi All,
Is anyone aware of an implementation of Test::Builder/Simple/More and
Test::Harness in JavaScript? The testing scene in JS appears pretty sad,
but I don't want to do much in JavaScript without a nice testing
framework. And Test::More would be my preferred way to go.
Sébastien Aperghis-Tramoni wrote:
Christopher H. Laco wrote:
I don't know if that answer your needs but Test::Distribution already
performs several kwalitee tests on the modules and other files of a
distribution.
http://search.cpan.org/dist/Test-Distribution/
Sébastien Aperghis-Tramoni
74 matches
Mail list logo
