I wanted an easier way to create test fixtures with DBIx::Class, so I wrote it.
I've written about it here:
http://blogs.perl.org/users/ovid/2014/02/easy-fixtures-with-dbix-class.html
Since this is the QA group, I feel that you might appreciate this more than
most. Bug reports and
should be able
to hook into that (or just take advantage of the fact that it's an OO feature
and use the normal timeout features with alarm that you would do for regular
classes.
1. https://github.com/Ovid/App-Prove-Plugin-ProgressBar
2. http://search.cpan.org/dist/Test-
o hit the CPAN or grab it
from github[5].
1.
http://search.cpan.org/dist/Fennec/lib/Fennec.pm#RUNNING_FENNEC_TEST_FILES_IN_PARALLEL
2.
http://search.cpan.org/dist/Test-Class-Moose/lib/Test/Class/Moose/Role/Parallel.pm
3. http://www.slideshare.net/Ovid/testcl
In case you haven't seen it, I now have an experimental branch of
Test::Class::Moose that provides built-in parallel testing.
http://blogs.perl.org/users/ovid/2013/12/merry-christmas-parallel-testing-with-testclassmoose-has-arrived.html
http://blogs.perl.org/users/ovid/2013/12/eating-m
Hi Shlomi,
My definitive answer would be to say "work with Leon" on this :) He's taken
over maintenance on TAP::Harness. I haven't looked at that section of the code
in quite some time and honestly, I don't have the time/energy to do so right
now.
Best,
Ovid
-
released. For example, the 'prove' utility calls App::Prove which calls
TAP::Harness. If others are using Test::Harness directly, perhaps Eric is right
and it should be deprecated? However, it's a core module and I don't know the
implications of that.
Cheers,
Ovid
--
IT
Here's a complete example of a TAP::Harness plugin to create a red/green
progress bar.
http://blogs.perl.org/users/ovid/2010/05/making-testharness-output-a-progress-bar.html
Cheers,
Ovid
--
IT consulting, training, international recruiting
http://www.allaroundtheworld.fr/.
Buy my
- Original Message -
> From: Karen Etheridge
>
> On Sun, Jul 07, 2013 at 02:45:22AM -0700, Ovid wrote:
>> Were I not so bandwidth-constrained, this would be less of an issue, but
> I'd like to see a good Wiki page or something with the pro/con arguments
>
- Original Message -
> From: Ricardo Signes
>
> * Leon Timmermans [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
ngle process instead of multiple
processes.
Or maybe profiling exposes issues that weren't previously apparent.
Or you fall back on a truncating strategy instead of rebuilding
(http://www.slideshare.net/Ovid/turbo-charged-test-suites-presentation). That's
often a lot faster.
There are so
xtends' in the import list here to look more
>Moose-y?
I think "extends" might be better. Good call.
I don't use standard inheritance because the various solutions for that don't
allow for both inheriting from a class and exporting functions (in this case,
ok(), i
re anything you would change? (It's
trivial to assert plans for classes and the entire test suite rather than rely
on done_testing(), but I haven't done that yet).
Cheers,
Ovid
--
Twitter - http://twitter.com/OvidPerl/
Buy my book - http://bit.ly/beginning_perl
Buy my other book - http://www.oreilly.com/catalog/perlhks/
Live and work overseas - http://www.overseas-exile.com/
thods
(startup/setup/teardown/shutdown), you could drop something like this in your
base class:
# see also http://www.slideshare.net/Ovid/a-whirlwind-tour-of-testclass
sub setup : Tests(setup) {
my $test = shift;
$test->reset_singletons;
}
Yes, it's a hack
From: Jeffrey Thalhammer
>To: Ovid
>Cc: Paul Johnson ; "perl-qa@perl.org"
>Sent: Monday, 1 October 2012, 22:48
>Subject: Re: TPF Devel::Cover grant report Week 18
>
>
>On Oct 1, 2012, at 2:00 AM, Ovid wrote:
>
>> For others: yes, I know that PPI off
setup/teardown/shutdown test control methods.
Cheers,
Ovid
--
Live and work overseas - http://www.overseas-exile.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter- http://twitter.com/OvidPerl/
king questions like this in various places on the Web. A
cookbook of examples would be lovely :)
Cheers,
Ovid
--
Live and work overseas - http://www.overseas-exile.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid
nested TAP, but the format is
backwards-compatible, allowing us to still deliver correct results (this
assumes that the "summary line" success or failure matches the success or
failure of the nested TAP.
Cheers,
Ovid
--
Live and work overseas - http://www.overseas-exile.com/
Buy the b
ways works!
Try it on a Test::Class test suite running thousands of test in a single
process, whizzing past on your terminal :)
Cheers,
Ovid
--
Live and work overseas - http://www.overseas-exile.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter - http://twitter.com/OvidPerl/
, as Schwern pointed out, that's why
I wrote Test::Most :)
> What I don’t like about duplicating `use` is that you need to diddle
> internals and ...
I think Schwern's not arguing against this. He's just trying to figure out the
best way forward.
Cheers,
Ovid
--
Live and w
Trap::Builder::SystemSafe;
use Test::Trap::Builder;
use Test::Trap;
use if eval "use PerlIO; 1", 'Test::Trap::Builder::PerlIO';
ok 1, 'All modules loaded successfully';
$ok = 1;
Cheers,
Ovid
--
Live and work overseas - http://www.overse
ou're using the actual use builtin and not worrying about extra
code that might or might not be obscuring problems.
Cheers,
Ovid
--
Live and work overseas - http://www.overseas-exile.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter - http://twitter.com/OvidPerl/
:
perl -MDB::Color -e some_program.pl
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter - http://twitter.com/OvidPerl
expecting an exact
text match.
In any event, I can't tell how to reproduce the issue from the plethora of
modules you've listed. Can you send a small code example of a test failure?
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter - http://twitter.com/OvidPerl/
ia would be hard in a code base small enough to
get your head around easily but maybe something smaller helps?
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blog
er issue at the same time.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter- http://twitter.com/OvidPerl/
--
o_output;
binmode $output, ':encoding(UTF-8)';
$output = Test::Builder->new->failure_output;
binmode $output, ':encoding(UTF-8)';
But I'd really like a clean way of just saying "kill my code if I ever see
'Wide character in print'
they'll definitely think twice.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter- http://twitter.com/OvidPerl/
e::Role and it adheres much more closely to the traits spec, particularly
with regards to the commutative and associative properties that Role::Tiny and
Moose::Role ignore (https://metacpan.org/module/Role::Basic::Philosophy)
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com
>
> From: David E. Wheeler
>
>On Nov 22, 2011, at 5:11 AM, Ovid wrote:
>
>> Ah, just saw this. As I've already said privately, but maybe we can see how
>> others feel, this is a PERFECT time to discourage use_ok and require_ok and
e, people have to work around their
limitations, and they don't add value.
http://use.perl.org/~Ovid/journal/39859
I'm hard-pressed to think of a better time to at least slip a note in the docs
that their use is discouraged.
Cheers,
Ovid
--
Live and work overseas - http://overseas
ousand cuts. Dave, you weren't
on the PIPs team when I optimized their test suite, but it was those "thousand
cuts" that I stripped away one by one to get an hour long test suite running in
less than 15 minutes.
So yeah, this is a very important issue. If performance isn't d
y. The name change
> tells the user this is not their father's Kansas.
>
> Besides, "tee bee two" rolls off the mouth nicely and TB:: is a bit
> too short.
Tee bee and not tee bee two? That is the question. Whether to suffer the
slings and arrows of outrageous attemp
care (with caveats, of course)
$test->SUPER::startup;
...
}
It's much cleaner that way.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter - http://twitter.com/OvidPerl/
Should have been sent to the list, not just Fergal.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter- http://twitter.com
revisited? When I find conceptually
simple ideas hard to do, I find it a code smell. (note that I'm not saying the
actual design is bad. I haven't looked). I also find subtests so incredibly
convenient and opens up so many possibilities that I would hate to lose them
(and I use
recognize this issue and be able to help.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter- http://
t; Python) utilizing its TAP support.
>
> See the full announcement and more ressources here:
>
> http://developer.amd.com/zones/opensource/AMDTapper/Pages/default.aspx
Looks interesting, but did they really release a separate distribution for
every
module in Tapper?
http://sear
the test history and I had started that
with https://github.com/Ovid/app--prove--history, but it's an awful hack which
I
hadn't gotten around to finishing.
I'll be at the QA Hackathon here in Amsterdam this weekend, so maybe I
should resurrect this idea?
Cheers
tallation).
At this point, I would suggest that Test::More might be for code that you put
on
the CPAN (assuming you don't want to force dependencies on people), but I'd
never want to do without Test::Most for personal code.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exi
aybe the 5 isn't present. However, for any contained array reference its
exact data can't change. However, if those came back in the order of
6,5,4,3,2,1, the test should fail (thus, I can't use bag tests).
Does anyone know of any test modules which allows this?
Cheers,
Ovid
--
extremely constrained environment for this particular case and trying to
determine my best options :/
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://blogs.perl.org/users/ovid/
Twitter- http://twitter.com/OvidPerl/
of items, but I'm pulling real
data (and it's very hard not to pull real data for this use case) and that data
will *usually* be in the order I expect, but subtle variations are allowed and
cannot be easily prevented. Unfortunately, I can't tell you more than this.
Cheers
structure
> (including nesting if you feeling really fruity),
Ooh, I would love to see that! After feedback from folks on that blog entry,
I'm sure something could be whipped up.
Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book - http:
--- On Thu, 17/2/11, Ovid wrote:
> From: Ovid
> I've stumbled on a bit of an odd case where I have
> constantly shifting data I need to test. Ordinarily I would
> use cmp_deeply from Test::Deep, but it's not quite
> structured enough. I need something similar to a Le
ut the 2 and 4 records are swapped
or maybe the 5 isn't present. However, for any contained array reference its
exact data can't change. However, if those came back in the order of
6,5,4,3,2,1, the test should fail (thus, I can't use bag tests).
Does anyone know of any test modules
back to perl-qa that
there
> would be more discussion?
I'd like to see it back in perl-qa, if only so that the people on perl-qa who
might be impacted can see what's going on.
And I suspect you'd get more response.
Cheers,
Ovid
--
Live and work overseas - http://overseas
ut, right?).
So did I do the wrong thing here? I'd love to hear pro and con arguments.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://blogs.perl.org/users/ovid/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
you might offer people the option of connecting live, but
also making it clear that you only support version X.
Again, there are numerous strategies you can take but the right one(s) will
depend on your needs.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech
you can just do this:
use My::Custom::Test::More tests => $test_count;
The advantage here is that you have your own custom test behaviours nicely
controlled by one module and if you need to change them, you can do so in one
spot.
Or maybe you meant something else by "this&
$test->load_fixture($tag);
}
}
By being able to tag tests, you'd be able to:
* Load fixtures as needed.
* Load dependencies as needed.
* Run only '$tag' tests
* ... or anything else you can think of with tags
Yeah, I know it would be more work for you, but you'
nd then summarising at the bottom.
When that's done, I often cut-n-paste the summary at the top of the email and
only leave the rest if it is really necessary.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://blogs.p
ning tests in a
single process to ensure the data structure doesn't go away? Test::Class and
Test::Aggregate can both let you do this.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://blogs.perl.org/users/ovid/
Twitter
sed by both modules exporting a blessed function by default
> and Moose's one sets a prototype.
Since the core Scalar::Util::blessed has the same prototype, would you consider
adding this to Test::Deep?
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech b
I would love feedback (via actual use) of a development version of Test::Most
available at http://search.cpan.org/~ovid/Test-Most-0.21_04/. If you're not
familar with it, instead of this:
use strict;
use warnings;
use Test::Exception 0.29;
use Test::Differences 0.500;
king (or
something like that), but it works for chromatic's Modern::Perl, so I'm unsure
of what's happening. I can't debug what I can't reproduce (before anyone asks,
I've emailed the testers but they've not gotten back to me).
Cheers,
Ovid--
Buy the book
+--+
# Looks like you failed 1 test of 1.
test-diff.t .. Dubious, test returned 1 (wstat 256, 0x100)Failed 1/1
subtests
Cheers,
Ovid--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/
could argue that I'm saving them two characters :) (not to mention the
fact that I'd be forcing them to be explicit that they didn't *forget* strict
and warnings)
Thoughts?
Curtis--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use
For Test::Class fans:
Here's the announcement of my Test::Class::Most:
http://blogs.perl.org/users/ovid/2010/01/-package-sometestclass.html
And if you can't wait for the CPAN upload (I'm sure there's no burning desire
for this):
http://github.com/Ovid/Test-Class-Most
marketing perspective, the camel wins hand-down. From a legal
>perspective, what are the pros and cons? Frankly, I have no idea.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter
camel and how can we approach O'Reilly
regarding this concern? While it's certainly the trademark of a private
company, I doubt very seriously that O'Reilly would be terribly averse to
giving TPF plenty of leeway in using it (as past history has shown).
Cheers,
Ovid
--
Buy the book
"inactive" and
"old" all imply "dead". "History" implies more of a narrative.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
x27;ve had problems with --merge in the past because
of how it works, but I'm curious to know what this issue is.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
ourse, should not be done without tests and that brings us back to
the original issue :)
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Officia
that for a given set of
inputs for a given state, you get a particular set of outputs. run_ok()
doesn't really manage any of that. Am I missing something here? (I could very
well be).
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog-
generally needs an "or die" after it.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
STIC");
Tried to compile '$module_or_code'.
Exit status: $error
DIAGNOSTIC
}
return $ok;
}
compile_ok $0;
compile_ok $0, 'we compile';
compile_ok 'CGI';
compile_ok 'No::Such::Module'
--- On Mon, 9/11/09, Ovid wrote:
> From: Ovid
> The *only* use I've ever had for use_ok() has been in a
> t/00-load.t test which attempts to load all modules and does
> a BAIL_OUT if it fails. I'm sure there are other use
> cases, but if that's the only one
I've been toying with this thought for a while: discourage (not quite
deprecate) use_ok() and require_ok(). I've written up some of the problems
with the former (http://use.perl.org/~Ovid/journal/39859) and the latter still
has the "or die" problem.
For the life of me, I
--- On Tue, 27/10/09, Michael Peters wrote:
> From: Michael Peters
>
> > If you like the output and want to convert your own
> POD to typeset documents, you can check out my VERY alpha
> code at:
> >
> > http://github.com/Ovid/Pod-Parser-GroffMom
>
>
ed that article and uploaded it to
slideshare:
http://www.slideshare.net/Ovid/testing-with-testclass
You might want to read that article for a couple of reasons:
* To learn Test::Class (even experienced users will learn stuff)
* To give me feedback on how well my converter works :)
If you
nice, I don't want to play.
I'll dive back in sooner or later, though. I always do.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
That doesn't look like it's going to happen
any time soon, so telling me to add diagnostics to TODO tests doesn't help :(
Thus, I'm trying to think of a way of solving my problem now, not at some
hypothetical date in the future.
Cheers,
Ovid
--
Buy the book - http://www
for the TODO at that point.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
them
down, aggregated tests get lumped together. Lacking proper subtest support
(which might not mitigate the problem) or structured diagnostics (which could
allow me to attach a lot more information to TODO tests) at the end of the day,
I need an easier way of tracking this.
Suggestions?
Cheers,
Ovid
module will be installed, but
increasing the chance, if it's installed, that others who depend on it will
install successfully. Hopefully that will also make programmers more likely to
use it if it's already there.
Yeah, I know. That's not really nice :)
Cheers,
Ovid--
Buy the
Hi all,
I've altered Test::Builder to handle the cases where people are using the TB
singleton at the top of their test files. You can get a copy at
http://github.com/Ovid/test-more/tree/master if you want to test it.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/ca
the roof was fixed (or at lest less leaky). The great thing about
pointing out this issue and asking module authors to address this is that it's
NOT an emergency.
Now if you'll excuse me, I need to go play in the sunshine.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.
comment "what's a function call and what's an argument", I know
what you mean, but again, how can we think about something in a larger context
and see what we can accomplish? I want to try something new.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
I forgot to hit 'reply all' :)
Also, I had considered this:
have $some_value, assuming { shift > 7 }, reason "Argument must be greater
than 7";
And that would allow us to naturally put complex constraints onto the values.
Cheers,
Ovid
--
Buy the book -
interface is great, why not? If it's bad, what would people *love* to see in a
test interface which allows them to naturally write tests?
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter
on $some_reason);
That's also ugly and requires the (&) prototype (and friends).
Thoughts? Am I totally smoking crack here? If there's a clean way to shoehorn
diagnostics on the Test::More-style interface, I guess that would be ok.
Cheers,
Ovid
--
Buy the book - http://www.or
as all the builder() method does is call
Test::Builder->new (and that's what I did in Test::JSON, to be honest). I
can't say whether or not this behavior will change in the future. I just used
the information passed to me by Schwern and by the Test::Builder::Module
do
>From http://use.perl.org/~Ovid/journal/39193
The latest developer release of Test::More allows subtests. Subtests are great
in that they solve a lot of
problems in advanced Perl testing, but they have required a change in
Test::Builder. Previously you could do stuff like this:
package T
(Helps if I send this from a subscribed address):
From http://use.perl.org/~Ovid/journal/39193
The latest developer release of Test::More allows subtests. Subtests are great
in that they solve a lot of problems in advanced Perl testing, but they have
required a change in Test::Builder
- Original Message
> From: Michael G Schwern
>
> Ovid wrote:
> > First feature request: automatic Moose support to build random data which
> > conforms to Moose constraints :) (Yes, I know it's much, much harder than
> it sounds).
>
> Hello, w
te yet more
> random data quickly.
First feature request: automatic Moose support to build random data which
conforms to Moose constraints :) (Yes, I know it's much, much harder than it
sounds).
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog
- Original Message
> From: Michael G Schwern
>
> Ovid wrote:
> >
> > I've generally been extremely pleased with how robust 'local
> > $hash->{value}'
> is,
> > but you can't localize lexical variables.
>
> The Test:
ception thrown that T::H::A should catch?
Test::Builder exits with 255 on a bail out. TAP::Harness dies. Maybe an
exception would be better here.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter
So
if the 'some subtest' subtest didn't emit anything until
that summary 'ok 1' line, can we safely run subtests in parallel
without worrying about whether or not their output overlaps?
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
T
think that's safe, but would a clone be safer? We have file handles stored
in $test and I'm unsure of the behavior there or how to safely test that.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
surprise!
};
Of course, you don't get something for nothing.
Oh, and I just uploaded a new Test::JSON to make sure it works with subtests :)
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter
catch all of the cases I've seen. It might be a useful stop-gap measure, but it
also seems dodgy as hell :(
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
- Original Message
> From: David E. Wheeler
> To: Ovid
> Cc: perl-qa@perl.org
> Sent: Monday, 29 June, 2009 17:38:15
> Subject: Re: Subtest fail with singletons
>
> On Jun 29, 2009, at 2:19 AM, Ovid wrote:
>
> >my $Test = Test::Builder->new
:XML (and other testing modules) which causes this issue.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog- http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.p
1..1
Cannot run test (Singleton fail) with active children at
/home/ovid/pips_dev/work/Pips3/branches/rights_modeling/deps/lib/perl5/Test/XML.pm
line 57.
# Child (FAIL!) exited without calling finalize()
The reason this happens is because Test::XML, at the top of its code, h
ok 4 - Setup should be called once for each test program
ok 5 - ... as should teardown
ok
All tests successful.
Files=1, Tests=5, 1 wallclock secs ( 0.02 usr 0.00 sys + 0.11 cusr 0.01
csys = 0.14 CPU)
Result: PASS
Cheers,
Ovid
--
Buy the book - http://www.orei
nt, I'm completely mystified why anyone has a problem with the
"subtest $name, sub { ...}" syntax. Honestly :)
But since I don't have a clue and am not particularly fussed, I'll just bow out
and let you folks have at it.
Cheers,
Ovid
--
Buy the book - http://www.oreill
noying bit of
> syntax. Were you worried that "text" might get lost at the end of the sub?
I would prefer the 'subtest {}, "text"' syntax, but you're right, the concern
is the text getting lost at the end. It's especially bad if you have a really
long b
ress in that subject ?
>
> tl;dr version: Yes, its resolved at least to Ovid and I's satisfaction who
> were the two most worried about it.
>
> Ovid and I talked about it first thing at the latest QA hackathon. Ovid,
> correct me if I'm wrong but...
>
> 1) /^[a-z
t your string as the value
of a key and it would magically work.
So hypothetically, you could do this:
while ( my $result = $parser->next ) {
if ( $result->is_yaml ) {
display($result->data->{ascii_art});
}
}
Cheers,
Ovid
--
Buy the book - http://www
1 - 100 of 785 matches
Mail list logo
