Re: ExtUtils::MakeMaker, and t/ sub-directories

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/? I've g

ExtUtils::MakeMaker, and t/ sub-directories

[ 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/? I've got a bunch of tests, and rather than client-ls.t, client-add.t, client-commit.t, etc, I'd like

Re: Test::More and Fatal

Chris Dolan wrote: I don't like that very much. The implicit die() on test functions will probably confuse subsequent readers of the code. # Cause the listed functions to die on error use Fatal qw(...); Furthermore, I cannot believe that ALL of your tests are critical. 150 or so out

Test::More and Fatal

Has anyone ever used Test::More and Fatal together? I have a test script, where each test builds upon the work of the previous step (it's part of the Subversion Perl bindings test suite, and it checks out files, makes changes to them, commits them, and so on). If any of these tests fails I ne

Re: Using pip to get testing done better and faster...

Adam Kennedy wrote: Since I moved to SVN, one of the things I've been doing is commiting my release tarballs into a /releases/ directory. One side-effect of this is that even before I've uploaded it to CPAN, ever release already has a URI. Eugh. Have you considered using SVN::Notify::Snapsh

Re: Sparse Test Output

Michael Peters wrote: Jonathan Rockway wrote: That said, I am willing to clean it up when I have time, and hopefully be able to provide a libtap that makes TAP support easy for any language. There is already a libtap - http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html Indeed. Is an

Re: OT: use.perl journals

A. Pagaltzis wrote: * David Cantrell <[EMAIL PROTECTED]> [2006-08-23 09:35]: You probably want http://use.perl.org/~username/journal/rss Actually, – as well as . The scraper pulls the la

Re: TAP ain't "Test All Perl"

A. Pagaltzis wrote: * Adrian Howard <[EMAIL PROTECTED]> [2006-08-22 12:25]: Like anybody reads my use.perl journal :-) There is a bunch of people who read all the use.perl journals, courtesy of … Indeed. /me wishes for a full contents RSS feed.

Re: Lessons from the test function parameter placement quibbles?

chromatic wrote: (My mind idly wonders if it were possible to generate this test description... somehow... somewhere) That's what I do with my Test:: modules. The test description is optional, and if not provided the module generates a (hopefully) sensible default. N

Re: TAP Namespace Nonproliferation Treaty

Ovid wrote: - Original Message From: Nik Clayton <[EMAIL PROTECTED]> Ovid wrote: I'm perfectly comfortable with this idea, but what I'm trying to figure > > out then, is the namespace for my parser. It's a TAP parser, after all. > > Any

Re: TAP Namespace Nonproliferation Treaty

Ovid wrote: I'm perfectly comfortable with this idea, but what I'm trying to figure > out then, is the namespace for my parser. It's a TAP parser, after all. > Any suggestions? I see that Adam has suggested a TAPx:: namespace, > but there could still be competing TAPx::Parser modules. Don't kn

Re: Continuous testing tools

Geoffrey Young wrote: Since you're using C++, you can probably use libtap (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the tests and then you could use a Perl harnes to collect those results. just out of curiosity

Re: SVN::Web

Nik Clayton wrote: Hi Adam, [...] Mea culpa -- that was supposed to be an e-mail. N

SVN::Web (was: Re: Fwd: Insurrection account created)

Hi Adam, Adam Kennedy wrote: Phase N is my company, and http://svn.phase-n.com/svn/cpan is the collaborative subversion repository for my code, that now includes PPI, which you've expressed a desire to have bugs fixed in I believe a number of times. I see you're using Insurrection. I was wo

Testing with Apache/mod_perl

Is Apache::Test the current state of the art when it comes to testing that web apps work as expected? I'm working on fleshing out the test suite for SVN::Web. I've already got tests that verify that the basic functionality works, that generated links are sane, and so on. But I've been bitte

Re: Best practice for version control of locally installed CPAN modules

Matisse Enzer wrote: Currently we are evaluating these options: 1) Maintain a list of the .tar.gz files and install from CPAN, for example M/MA/MATISSE/Text-TagTemplate-1.8.tar.gz 2) Put the CPAN .tar.gz files in a local CPAN repository and use CPAN::Site to install - that way we

Re: Surprising use_ok false positive

Chris Dolan wrote: Advice? While this example is contrived, the "eval { require ... }" idiom is used often in the wild, so this is not a wholly unrealistic scenario. Real-world example. SVN::Web uses this idiom to determine whether to use CGI or CGI::Fast. Even if CGI::Fast is installed i

Re: Test::More & Test::Builder::Tester

Michael G Schwern wrote: On Sat, Oct 08, 2005 at 06:26:46PM +0100, Nik Clayton wrote: Define a new version of TAP with a single change. Specifically, emit a version number in the TAP output that describes the version of TAP that's being emitted. While this may be an interesting idea

Re: Test::More & Test::Builder::Tester

Michael G Schwern wrote: I don't have a long term solution for users of test_diag(). I'm entertaining ideas. "Don't change the failure output" is not one of them. One temporary hack is to parse the test_diag() input, look for attempts to match the old Test::More diagnostics and translate it in

Kwalitee and Perl::Critic

I don't have strong opinions about this yet, but has anyone else looked at the Perl::Critic suite of modules on CPAN? It occurs to me that: a) Kwalitee metrics could quite easily be implemented as Perl::Critic plugins. b) The plugins that it ships with (based on Perl Best Practices) may for

Re: Why are we adding more kwalitee tests?

Chromatic wrote: Maybe the problem is that CPANTS as it exists now measures some metrics better measured on the developer side, not the installer side. It's handy to run the POD coverage tests as the developer of a module, but it's not that interesting for the person installing the module to run

Re: Basic Testing Questions

Michael G Schwern wrote: On Mon, Jul 18, 2005 at 09:42:06AM -0400, Brett Sanger wrote: There are some tests that I would love to have abort as soon as they fail. (If step 3 failed, then steps 4 and 5 are places I don't want to go) Is there a way to make prove do this? I skimmed the Test::Build

Re: Test::Cmd -- Recommended?

Ian Langworth wrote: On 7/8/05, James E Keenan <[EMAIL PROTECTED]> wrote: One other curiosum: As a result of my Phalanx work, I've gotten in the habit of using File::Temp to create 'anonymous' directories and files in which to conduct testing. This is one of the many features of Test::Cmd,

Backwards (?) kwalitee definition on qa.perl.org

http://qa.perl.org/phalanx/kwalitee.html says: What is kwalitee? Kwalitee is inexact quality. We don't know exactly what it is, but we know it when we see it. Isn't that backwards? I thought 'kwalitee' was supposed to be a metric that was exact, and that (hopefully) had some corr

Self-testing kwalitee

Having been a little more prolific on the module front recently I'm interesting in making sure that my own modules pass the kwalitee tests. Preferably before I put them on CPAN. But poking through qa.perl.org I can't find anywhere that these tests are actually rigorously defined. The closes

Re: AnnoCPAN and a wiki POD idea

Michael G Schwern wrote: So where's the RSS push interface so I don't have to go checking 2983 RSS feeds every day to see if there's anything interesting? Call me a snob, but O(1) is still better than O(n). PS Its entirely possible I'm just ignorant. www.bloglines.com for an example of somet

[ANNOUNCE] Test::Unix::Group

The uploaded file Test-Unix-Group-0.01.tar.gz has entered CPAN as file: $CPAN/authors/id/N/NI/NIKC/Test-Unix-Group-0.01.tar.gz size: 6455 bytes md5: 497cba10cde46dcfb8f48b1de7238f8e From the docs: SYNOPSIS use Test::Unix::Group tests => 4; group_ok({ name => 'wheel

[ANNOUNCE] Test::Unix::User

The uploaded file Test-Unix-User-0.01.tar.gz has entered CPAN as file: $CPAN/authors/id/N/NI/NIKC/Test-Unix-User-0.01.tar.gz size: 7007 bytes md5: c3506dce32b5f841b1e6e7e351757556 From the docs: SYNOPSIS use Test::Unix::User tests => 2; user_ok({ name => 'nik', uid

Re: [ANNOUNCE] Test::Symlink

Steve Peters wrote: My concern with symlink_ok() is that I'll go to use it and have to repeatedly check the syntax to see which should be the link and which should be the file. That's why the docs suggests using Perl's fat comma operator as an aid. I agree, symlink_ok('foo', 'bar'); is a

Re: [ANNOUNCE] Test::Symlink

Michael, Thanks for your comments. Michael G Schwern wrote: [re-ordered slightly] There's no example code in the SYNOPSIS. > Your example code which uses Test::Symlink should show how to set up the plan. Namely: use Test::Symlink tests => 2; > > It would be nice to see an example of the gen

Re: [ANNOUNCE] Test::Symlink

Ivorw wrote: I have a concern on this relating to portability. How will the module behave on platforms that don't have symlinks? In theory symlink_ok() will automatically skip any tests that it's asked to do if symlinks aren't supported. Since I don't have systems that I can test it on wher

[ANNOUNCE] Test::Symlink

The uploaded file Test-Symlink-0.01.tar.gz has entered CPAN as file: $CPAN/authors/id/N/NI/NIKC/Test-Symlink-0.01.tar.gz size: 4123 bytes md5: 9a3797b3d94c3ad73b061bd7b1aa2134 Test::Symlink is the first in a series of modules that I'm writing. They differ from many of the modules

Test::Builder::Tester vs. Test::Tester

As I write my first set of Test::Builder based tests I'm looking for a way to test the tests themselves, and make sure that they're doing the right thing. A quick peruse of CPAN has thrown up Test::Builder::Tester and Test::Tester. I've seen quite a few modules that use Test::Builder::Tester,