On Apr 4, 2007, at 1:41 PM, Eric Wilhelm wrote:
What I was thinking of here was more along the lines of how to get
Test::Class to play that game.
It already does. I routinely do stuff like this with Test::Class:
env TEST_METHOD='student_.*' ./Build testcover
to test, say, the student port
On Wednesday 04 April 2007 11:41, Eric Wilhelm wrote:
> # from chromatic
> >It seems to me that we already have a good way of separating tests per
> > their behavior: separate test files and even separate test
> > directories.
> Correct. See my other post and the test profiles thing in
> Module
# from chromatic
# on Wednesday 04 April 2007 11:24 am:
>> Can we think about this in terms of the producer supporting some
>> sort of dynamic skip concept involving labels or such? Possibly a
>> bit of yaml shoved in an environment variable?
>
>It seems to me that we already have a good way of s
On Wednesday 04 April 2007 11:11, Eric Wilhelm wrote:
> Can we think about this in terms of the producer supporting some sort of
> dynamic skip concept involving labels or such? Possibly a bit of yaml
> shoved in an environment variable?
It seems to me that we already have a good way of separati
# from Philippe Bruhat (BooK)
# on Wednesday 04 April 2007 05:42 am:
>Usually because I want to run a specific subset of tests only.
>
>A typical example is:
>
> $ AMS_REMOTE=1 perl -Ilib t/90up2date.t simpsons
> 1..26
> # Testing 13 themes using the network (may take a while)
> ok 1 #
# from Andy Armstrong
# on Wednesday 04 April 2007 05:58 am:
> runtests t/*.t --select regression,docs
>
>Would select only regression and documentation tests. That's just an
>example plucked out of the ether of course - it wouldn't /have/ to
>work like that.
Meaning that every test has to d
On 4/4/07, Philippe Bruhat (BooK) <[EMAIL PROTECTED]> wrote:
I've found myself passing parameters to some of my tests scripts.
Usually because I want to run a specific subset of tests only.
...
Thoughts, anyone?
Wonderful idea. I'll take it off of my list of things to bring up someday.
I oft
Le mercredi 04 avril 2007 à 13:58, Andy Armstrong écrivait:
>
> If you're running more than one test script with runtests / prove
> you'll presumably be sending the same arguments to all of them. So it
> might make sense to think about a standard(ish) vocabulary for args -
> so that:
>
> r
--- "Philippe Bruhat (BooK)" <[EMAIL PROTECTED]> wrote:
> These parameters are obviously tightly linked to the test script
> itself,
> but I think it would be nice if prove allowed me to pass arguments to
> my test scripts. Naturally, it would be my responsibility, as the
> developer of the test s
Philippe Bruhat (BooK) wrote:
> Hi,
>
> I've found myself passing parameters to some of my tests scripts.
> Usually because I want to run a specific subset of tests only.
>
> A typical example is:
>
> $ AMS_REMOTE=1 perl -Ilib t/90up2date.t simpsons
Why not use an environment variable? You
On 4 Apr 2007, at 13:42, Philippe Bruhat (BooK) wrote:
Would it make sense to patch Test::Harness (and Test::Harness::Strap)
so that _command_line() would be able to create a command-line with
parameters?
Thoughts, anyone?
It sounds like a sensible idea to me. It'd probably make more sense
t
Hi,
I've found myself passing parameters to some of my tests scripts.
Usually because I want to run a specific subset of tests only.
A typical example is:
$ AMS_REMOTE=1 perl -Ilib t/90up2date.t simpsons
1..26
# Testing 13 themes using the network (may take a while)
ok 1 # skip A
!
YAPC::Europe 2007 is looking for people who would like to moderate a ~3
hour hackathon on e.g. Perl Testing, TAP, etc.
You can find more information on what we're looking for and what we can
offer to moderators (eg travel funding) on our website:
http://vienna.yapceurope.org/ye2007/cfh.html
13 matches
Mail list logo
