IPC::Open3 failure on Windows

$stuck eq $begging). I know from talking to Jos Bouman that IPC::Cmd has apparently solved this problem, but I can't figure it out from his code. Groveling, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Thoughts about test harness summary

the test name. I deliberately made it easy to subclass TAPx::Harness. While it's not perfect (lots more work to do), all you need to do is override the 'summary' method to generate any sort of test summary you like. Then you can just use it: runtests --harness My::TAPx::Harnes

Test::Builder feature request

My::Test::More tests => $tests' in your code. That will always set the environment variable and provide some measure of safety. That protects someone accidentally running 'perl t/test.t', but clearly the harness really isn't active then, so it's a bit of a h

Re: Test::Builder feature request

--- Nadim Khemir <[EMAIL PROTECTED]> wrote: > On Thursday 11 January 2007 15:30, Ovid wrote: > > Quite often people will write code which tests to see if > > $ENV{HARNESS_ACTIVE} is true. For example, this allows them to not > > email support from their code while tes

Re: Test::Builder feature request

he real world, it's not always practical to avoid this, particularly when you are adding tests to an old, untested code base and you need to get tests in place prior to refactoring. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

RE: Test::Builder feature request

support tickets get sent out, and so on. So I guess that while everyone else has the luxury of working with systems which are clean enough that it's not too expensive to work around issues like this, I'll shelve this suggestion and go back to the real world and continue trying to cl

Re: Test Coverage vs. Refactoring

ere, at last count, 50,000 properties in the database. Code coverage was the easy bit. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Dealing with balls o' mud (was: Re: Test::Builder feature request)

the issue that sometimes you absolutely don't want to run the code because some of the things it does can be dangerous or problematic, hence the (admittedly awful) hack of sometimes modifying the code to check to see if we're testing. That hack, however, is easier to implement than the inn

TAPx::Parser 0.50_04

7;d be grateful. Cheers, Ovid 0.05_04 14 January 2007 - BACKWARDS IMCOMPATIBLE: Renamed all '::Results' classes to '::Result' because they represent a single result. - Fixed bug where piping would break verbose output. - IPC::Open3::open3 now takes a @comman

TAPx::Parser: 'wait' and 'exit' status on Windows

finished, $? appears to have the wait status on OS X and other *nix operating systems, but not on Windows. Any thoughts? One person has told me that they don't think it's applicable under Windows, but I don't think that's correct. Cheers, Ovid -- Buy the book -- http://www.oreilly

Re: TAPx::Parser: 'wait' and 'exit' status on Windows

internal Test::Builder function worked just fine, but that only works with tests using Test::Builder. I really think that TAPx::Parser is great and is something I'd love to see get moved into CORE, but until I can nail down a few final Windows issues, I can't see anyone agreeing to this

What the 'runtests' output looks like

(It would help if this is sent from the correct email address) Hi all, If you've not checked out TAPx::Parser lately, here's what the 'runtests' output looks like: http://publius-ovidius.livejournal.com/222624.html Cheers, Ovid -- Buy the book -- http://www.oreilly

What the 'runtests' output looks like

Hi all, If you've not checked out TAPx::Parser lately, here's what the 'runtests' output looks like: http://publius-ovidius.livejournal.com/222624.html Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Config files for TAPx::Parser

ans of YAML. Other suggestions are welcome, but they need to be lightweight and either core modules or easy to embed. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Anonymous subversion access for TAPx::Parser

e are still some mysterious issues there, but we're getting closer all the time! Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

TAPx::Parser 0.50_06 -- Now on Windows!

because Andy looked into and saw that it's very invasive. We'd prefer to get things relatively stable before taking such a leap. Cheers, Ovid 0.50_06 18 January 2007 - Fixed doc typo in examples/README [rt.cpan.org #24409] - Colored test output is now the default for

Re: TAPx::Parser 0.50_06 -- Now on Windows!

to send, and > this mail happened to be on a more or less relevent topic. Thanks. I appreciate it! Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Test::Harness 3.0

;re the pumpkings and keeper of the keys. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Test::Harness 3.0

us their use is. I do know that a few people are overriding straps -- 'prove' even has a switch to let you override it directly -- and that might be an issue. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Test::Harness 3.0

e tests allow. Though the latest test results and comments for TAPx::Parser look promising, we don't have access to that 'wide variety of architecture'. How can we test something so key without throwing the switch? This concerns me, but I don't know enough about this area to rea

Re: Test::Harness 3.0

testing framework is simply too limited and most acknowledge that something new needs to come along. However, it's going to be awfully tough to come up with something new if we don't change *something*. I'm just worried about what it is we can safely change. Do Test::Smoke,

Re: Test::Harness 3.0

ng simple like 'All tests successful', then this is an easier task. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Test::Harness 3.0

call $harness->all_passed than $harness->{all_pased} (sic). Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

How many test files ship with 5.8.8?

files. What gives? Also, since I don't know makefiles terribly well, I can't figure out exactly how the test suite is getting invoked. That might help me with 'runtests'. Help? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Test::Harness 3.0

; document format). As of a couple of days ago (or maybe just yesterday, I can't recall) YAML::Tiny is now embedded as TAPx::Parser::YAML, so this would be easy. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Test::Harness 3.0

ikely to be used in TAP 2.0). And I do agree that TAP output is too limited for the current needs being discussed. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Updated TAP Grammar

once rewrote part of this to eliminate some performance issues. If you could forward that along, I'd appreciate it :) Cheers, Ovid (* For the time being, I'm cheating on the EBNF by allowing certain terms to be defined by POSIX character classes by using the following

Re: Updated TAP Grammar

Yup. Knew I shouldn't have done this now. --- Ovid <[EMAIL PROTECTED]> wrote: > tests ::= test {test} That's unused. > todo_directive ::= '#' 'TODO' ' ' {character} > > skip_directive ::= '#' 'SKIP'

TAP for skipping all tests

is only implied, not required. It seems to me that specifying how many tests you have should be fine: 1..13 # SKIP 'cuz thirteen is scary, dude Is there a reason for the '1..0' syntax or is that merely a convention? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog

Re: TAP for skipping all tests

--- Steve Peters <[EMAIL PROTECTED]> wrote: > My guess is that the number of test run may depend on things determined > after the point you decided to skip all the tests. Sounds reasonable, but I also think it should be optional. Cheers, Ovid -- Buy the book -- http://www.oreilly

Re: TAP for skipping all tests

--- Michael G Schwern <[EMAIL PROTECTED]> wrote: > Ovid wrote: > > http://search.cpan.org/dist/Test-Harness/lib/Test/Harness/TAP.pod implies > > that if I want to skip all tests, I need something like this format: > > > > 1..0 # SKIP why not? > > >

Re: TAPx::Harness support for EUMM

still to be able to plug in > any alternative harness. Agreed. Particularly since a large impetus of this project is to allow folks to write custom harnesses for their needs. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Test script with hierarchy

l of the [gui] tests passed, all of the [database] tests passed, etc. This allowed him to effective tag and group sets of test results and potentially (my thought, though not mentioned in the discussion) take actions if tests with particular tags fail. Cheers, Ovid -- Buy the book -- http://www.

Re: Parallelizing TAPx::Harness?

storing the TAP then becomes rather problematic. However, even though infinite streams are trivial, I don't know of anyone who's actually using them (they'd be useful, though). Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Fixtures

e when you have strange ordering dependencies, fail to clean up temp files, alter global state, etc. Test fixtures can make finding such code errors even more reliable because they guarantee (to the extent that they're not buggy) that every set of tests which runs has, if you will, the same st

Re: Fixtures

Nesse/FixtureCode Really? :) java.lang.NullPointerException fitnesse.wikitext.WidgetBuilder.addChildWidgets(Unknown Source) fitnesse.wikitext.WidgetBuilder.addChildWidgets(Unknown Source) fitnesse.wikitext.WidgetBuilder.addChildWidgets(Unknown Source) fitnesse.wikitext.WidgetBuilder.addChildWi

RE: Fixtures

:Database' has a DESTROY method which drops the database. At the beginning and end of every .t file, the database is created from scratch and destroyed. You can also create a test helper module which can populate the database with sample data (or at least static data which should always exist), though this means that the programmer looking at a test doesn't immediately see what data's in the database. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Fixtures

d rollback at the end. If you're using files, you can use File::Temp to automatically unlink the file at the end of the test run. In short, most things that we do in testing can be set up to clean up automatically at the end of a test run. Cheers, Ovid -- Buy the book -- http://www.oreill

Re: Test::Simple API incompatibility - cpan-testers FAIL results

this warning be spelled out even clearer, maybe even in big, bold letters or in its own section of the docs? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Regression Behaviour between TAPx-Parser-0.41 to TAPx-Parser-trunk

; my $self = shift; > > return if $self->is_unplanned; # <--- > > # TODO directives reverse the sense of a test. > return $self->has_todo ? 1 : $self->ok !~ /not/; > } This does appear to be a bug. I know how it came about and I'm l

Re: Regression Behaviour between TAPx-Parser-0.41 to TAPx-Parser-trunk

; > sub is_ok { > my $self = shift; > > return if $self->is_unplanned; # <--- > > # TODO directives reverse the sense of a test. > return $self->has_todo ? 1 : $self->ok !~ /not/; > } You noted that the 'bignum' test failed. Well, let's look at that one: print <http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Regression Behaviour between TAPx-Parser-0.41 to TAPx-Parser-trunk

might help. > And furthermore, I'm not sure I'll be > able to > rely on the new API until a stable version of TAPx::Parser 0.5x is > released, That's fair. We're working on getting a stable release (there are enough changes that it might bump up to 0.6). Thanks again

Re: Regression Behaviour between (correction!)

--- Ovid <[EMAIL PROTECTED]> wrote: > Can anyone else comment on this? I understand exactly where Shlomi > is > coming from and I know that he's wrong in his thoughts, but there is > certainly a difference of opinion regarding 'correct' behavior. I meant "

RE: Fixtures

--- Ovid <[EMAIL PROTECTED]> wrote: > Later, the 'Our::Test::Database' has a DESTROY method which drops the > database. At the beginning and end of every .t file, the database is > created from scratch and destroyed. I forgot to mention something very important if yo

Generating test data and testing it

e' methods to *not* be tests for the current scope. This allows us to use our tests as test fixtures rather than duplicate this logic. I think this is a horribly clumsy idea, but the above is a simplified example and some test data could get hairy to setup and if we change our Web pages,

Re: Generating test data and testing it

} > > ); > > Maybe I'm missing something, but in your second example, you declare > $override as a lexical and don't use it anywhere. May I inquire what > was your real intention? It holds the overrides in scope so that when $override is DESTROYed, we can ro

Re: use mocked

" means that your module pretty much doesn't work for our current code layout at work (I've other projects with this issue, too). Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: use mocked

--- Luke Closs <[EMAIL PROTECTED]> wrote: > On 2/22/07, Ovid <[EMAIL PROTECTED]> wrote: > > > > Telling me "you can only use t/lib for mocked modules" > > > Woah, dude. mocked.pm loads mocked modules from t/lib. You can use > t/lib > for

UNIVERSAL::require broke my tests

this sort of error down, but it's not great that the code mysteriously stops working. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: UNIVERSAL::require broke my tests

--- Ovid <[EMAIL PROTECTED]> wrote: > #!/usr/bin/perl > > use strict; > use warnings; > > use UNIVERSAL::require; > use HTML::TokeParser qw; > > print "here"; > > That produces: > > :!perl -Ilib parse.pl > "n

UNIVERSAL::require broke my tests

this sort of error down, but it's not great that the code mysteriously stops working. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Managing Test Plans with Vim

ine I'm currently editing since I'm presumably wanting to add or alter some tests. It really helps with the minor test plan annoyance. Note: I'm using 'Leader' to set my leader to ',' for the plugin. If you do that, you might want this in your .vimrc: let

Re: Managing Test Plans with Vim

--- Ovid <[EMAIL PROTECTED]> wrote: > Given the recent talks about test plans, here's what I have in > .vim/plugin/ToggleTestPlan.vim: *snip* Given all of this chat, what would folks think about an optional switch to 'runtests' (the TAPx::Parser equivalent to '

Re: Managing Test Plans with Vim

itch, though, as 'warnings' is already taken to enable warnings in the programs. '--tap-warnings' is probably a decent choice even though I prefer '--squeal-like-a-pig'. (Well, -w and -W are taken, '--warnings' is not, but '--warnings' seems like it would be too confusing) Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Managing Test Plans with Vim

ning on doing a new dev release tonight (pretty much what's in Subversion right now), so it won't be in there right away, but I do like this idea. Any other thoughts on warnings would be great. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI --

Re: Managing Test Plans with Vim

--- Andy Lester <[EMAIL PROTECTED]> wrote: > > On Mar 5, 2007, at 8:16 AM, Ovid wrote: > > > Sounds reasonable. I'm planning on doing a new dev release tonight > > (pretty much what's in Subversion right now), so it won't be in > there > >

Re: Managing Test Plans with Vim

hip who'll write the Eclipse TAP plugin. Hey, we all > have our vices, I like Eclipse. :) > > So I'd do something like. > > rc_file: /home/ovid/.runtestsrc If so, you definitely want TAPx::Parser and its 'runtests' utility instead of the normal Test::Harness/pr

TAPx::Parser -> TAP::Parser?

I realize that enough people are using TAPx::Parser that it might be a tiny speed bump for some, but I can't see any major difficulties here. Any concerns/objections? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

TAPx::Parser -> TAP::Parser?

might be a tiny speed bump for some, but I can't see any major difficulties here. Any concerns/objections? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: TAPx::Parser -> TAP::Parser?

tribution. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Paying for TAP 2.0

ur work to improve Perl's testing tools. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Paying for TAP 2.0

rably with enough people on this list giving it a ++), I'd be likely to vote to approve funding for such work, though I can't speak for the rest of the grant committee. This would be the next logical step in our work to improve Perl's testing tools. Cheers, Ovid -- Buy the book

Re: Paying for TAP 2.0

ons (exception tests, eq_or_diff, etc) * Output TAP 2.0 (line numbers for failures, clear diagnostics, etc) * Wash my dishes Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Paying for TAP 2.0

--- Fergal Daly <[EMAIL PROTECTED]> wrote: > On 07/03/07, Ovid <[EMAIL PROTECTED]> wrote: > > --- Andy Armstrong <[EMAIL PROTECTED]> wrote: > > > > > Where does TAP::Tests fit in? D'you mean as an alternative to > > > Test::More or wh

Minor Test::Class issues

s ( 0.11 cusr + 0.03 csys = 0.14 CPU) Failed 1/1 test programs. -1/5 subtests failed. I note that '# Foo->some_test' isn't showing up with 'runtests', so I'll have to look into that. but other than that, we have the same issues. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Minor Test::Class issues

--- Adrian Howard <[EMAIL PROTECTED]> wrote: > > On 8 Mar 2007, at 10:44, Ovid wrote: > [snip] > > I cannot easily use 'Test::NoWarnings' because that adds an extra > > test, > > thus forcing me to use 'no_plan' with one of my tests. Is the

Customizing Your Test Modules

Also at http://use.perl.org/~Ovid/journal/32614 I get tired of writing this all the time: #!/usr/bin/perl use Test::More tests => 23; use Test::Exception; use Test::Differences; use Test::NoWarnings; ... I write that *a lot*. No more. This does the same thing: #!/usr/bin/p

Re: Minor Test::Class issues

he code out into your > subclass and rename appropriately. You'll just need _isa_class() and > _test_classes(). That, by the way, has worked perfectly. Thanks! Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Paying for TAP 2.0

t; > This seems safer than generating it by default. Agreed. You can get this behavior with "runtests" by passing the '-f' switch (--failures) switch. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: How would I use TAPx::Harness to run C++ TAP output?

ime: $ runtests --execrc my_execrc t/* t/perl...ok t/tap Failed 1/3 subtests Test Summary Report --- t/tap.exe (Wstat: 0 Tests: 3 Failed: 1) Failed tests: 2 Files=2, Tests=5, 0 wallclock secs ( 0.04 cusr + 0.00 csys = 0.04 CPU) Note that the

Re: run C++ TAP output? (even easier)

ts --exec bin/run.pl t/tap Failed 1/3 subtests t/perl...ok Test Summary Report --- t/tap.exe (Wstat: 0 Tests: 3 Failed: 1) Failed tests: 2 Files=2, Tests=5, 0 wallclock secs ( 0.04 cusr + 0.00 csys = 0.04 CPU) Cheers, Ovid -- Buy the book

Re: nested groups in TAP

s and which we have significant agreement on, I'm terribly reluctant to extend the TAP::Parser to handle this. Old TAP parsers need to read new TAP and still generate reasonable output. There are several ways we could accomplish the same thing without break backwards compatibility. Let's e

Re: nested groups in TAP

.2 ok 2 # outer block was all good 3 1..3 ok 3.1 ok 3.2 not ok 3 # planned for 3 but only ran 2 tests Both 'prove' and 'runtests' parse this correctly. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Worrying about ... (stop!)

amless an upgrade as possible. Any questions? No? Good, I didn't think so. You may now return to your regularly scheduled whinging (I'll even whinge myself, if it makes you feel better). Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Solution to synching STDOUT and STDERR?

fairly common complaint. But I think that provides us with our answer. The streams only need to be in synch when runtests (or prove) is in VERBOSE mode. There is no information lost and everyone's happy, yes? Otherwise, let STDERR be STDERR and the problem is solved. Does this work?

Re: The price of synching STDOUT and STDERR

miss in development. In fact, it's so useful that our custom 'Our::Test::More' here at work includes that by default. Of course, one could solve this problem by only using core modules ... Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Misunderstand setup in Test::Class?

Rather than repeat the entire post here, there is a conceptual problem with setup methods in Test::Class. I'm just not sure if the conceptual problem is mine or Test::Class's :) http://www.perlmonks.org/?node_id=604787 Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catal

Re: [tapx-dev] TAP::Parser, structured diagnostics

o; ... How do you mark that as a TODO test? not ok 2 # TODO don't know what $foo is #--- Anyone see a problem with that? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: [tapx-dev] TAP::Parser, structured diagnostics

--- Michael G Schwern <[EMAIL PROTECTED]> wrote: > Ovid wrote: > > So we have this: > > > > not ok 2 #--- > > - > > line: 17 > > test: ok $foo; > > ... > > Why do you keep putting everything in an array? Doesn't h

Re: [tapx-dev] TAP::Parser, structured diagnostics

ould still have enough info to say whether or not the test failed. Even if it hangs prior to displaying diagnostics, the programmer at least can see the test name and number and be able to take appropriate action. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Eliminating STDERR without any disruption.

TAP::Parser still keeps a test count and the YAML can simply have the test number embedded in it. Heck, at that point, you could even dump all of the YAML into a separate file and still know which YAML is associated with which test. No test number? It's not associated with a test. Cheers,

TAP::Parser internationalization

at the entire runtests output could be easier to follow. I have three questions: 1. How important is this feature? 2. Is a YAML phrasebook a sensible approach? 3. Where's my beer? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: Eliminating STDERR without any disruption.

sing TAP::Parser any way.Does anyone know of groups that are *regularly* using the TAP::Parser for test suites in other languages? I know of xmms2, but that's about it. I'd like to find more for some talks I have coming up and I'd also like to find a way to encourage other TAP produc

Re: TAP::Parser internationalization

ou use YAML.pm, at any rate. We've our own internal "YAMLish" parser, based on YAML::Tiny. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Custom Test::More problem

Here's the minimal test case: use lib 't/lib'; use My::Test::More 'no_plan'; sub foo { die 'some problem' if @_; return 1; } ok foo(), 'this lives'; ok foo(1), 'this dies'; And My::Test::More (a stripped

Re: Custom Test::More problem

fixed recently, yes?) In any event, I'll look at making this work. Thanks. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

use Test::Custom;

tion_imports; END if ( my $error = $@ ) { ... } However, I just *know* there are problems with this, but I can't think for the life of me what they might be. Does that seem sane to folks? Am I overlooking something blindingly obvious? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: use Test::Custom;

--- Adrian Howard <[EMAIL PROTECTED]> wrote: > Nice idea. Looking very like David Golden's ToolSet module, or > Damian's Toolkit. Could you extend one of those? Toolkit is a bit more problematic for my needs, but ToolSet looks interesting. Cheers, Ovid --

Re: Passing parameters to test scripts

o them: runtests --exec ./my_test_driver See the examples/README and the examples/my_exec for an example of how to do this (the particular example included runs tests written in Ruby, Perl, and validates a couple of Web pages). Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlh

Re: trying to setup Module::CPANTS::Analyse

anup=>$ENV{DONT_CLEANUP}, }); my $rv=$a->unpack; Switching $analyze to $a should work. However, it's not recommend to use the special $a and $b variables in this way since they're for sorting. Converting all of your $a variables to $analyze and using strict and warnings should help. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: trying to setup Module::CPANTS::Analyse

that you would lecture Schwern > like that. :-) I've cheerfully lectured Schwern about many things. I usually turn out to be dead wrong :) Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

SKIP without counting

one test skipped SKIP: { skip $connection->error, $remaining_tests } exit; } Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: SKIP without counting

--- Eric Wilhelm <[EMAIL PROTECTED]> wrote: > # from Ovid > # on Monday 16 April 2007 02:29 am: > > >I need to skip the > >rest of the tests, but I want to use a plan and I don't want to keep > >counting the number of tests after the skip. > ... > &g

Automocked objects

return a true value unless specifically overridden. I'd have to do tricks like overriding isa() and friends, but that seems like it would be a very lightweight method of handling mocked objects. Is there something which does this? Did I miss anything? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Re: "plan skip_all => $reason" is no plan?

se. ->has_plan should return a boolean value and ->plan should take over the ->has_plan behavior. However, we still have a bug: #!/usr/bin/perl use Data::Dumper; use Test::More; my $Test = Test::Builder->new; plan skip_all => "I'm leaving NOW!"; END

use_ok and %INC

In relation to this bug: http://use.perl.org/~Ovid/journal/33441 I had use_ok('Some::Module', @import_list) appear to succeed, even though it had not. The imports weren't imported and that's because I had a previous failure with: eval 'use Some::Module'

Re: .t files as specs

or I created something difficult to work with, I have bell tower/deer rifle fantasies. Cheers, Ovid

Fw: Test::Class fixture problem

I wondered why this never showed up in PerlQA. - Forwarded Message From: Ovid <[EMAIL PROTECTED]> To: [EMAIL PROTECTED]; Adrian Howard <[EMAIL PROTECTED]> Sent: Friday, June 29, 2007 4:23:15 PM Subject: Test::Class fixture problem I've just spent quite a bit of time de

Re: Trailing backslash in TAP lines

he regexes I've cobbled together for TAP parsing since there are so many edge cases. Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

Sequential Mocking with Test::MockModule

r away from the mocking, which could confuse some, but it would be much nicer to write! The code for this shouldn't be too hard, but I'm wondering if anyone thinks this is a stupid idea, or if something like this belongs directly in Test::MockModule? Cheers, Ovid -- Buy the book -- http://www.oreilly.com/catalog/perlhks/ Perl and CGI -- http://users.easystreet.com/ovid/cgi_course/

<    1   2   3   4   5   6   7   8   >