--- Smylers <[EMAIL PROTECTED]> wrote:
> > child directory I'm fairly certain of. I am certain that more than
> > one 'extra tests' directory is needed,
>
> Why are you certain of this? It seems far from obvious to me.
Because there are plenty of "extra" tests we could conceivably have
which
# from Smylers
# on Thursday 16 August 2007 11:40 pm:
>> I am certain that more than one 'extra tests' directory is needed,
>
>Why are you certain of this?
Because I already have a use for three 'profiles' in one project and I
can name a few others from elsewhere:
1. author (kwalitee, pod, e
# from Ovid
# on Friday 17 August 2007 12:40 am:
>> > As for the 'xt' name:
>>
>> Nobody is intuitively know what "xt" means
>
>Because 't/' is self-explanatory?
Yeah dude, it's like 't', but the x makes it eXtreme ;-)
--Eric
--
I eat your socks and you pay me.
--The business sense of a very sm
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 issues? I've used t/au
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/classes/pages/etc.
F
Ovid writes:
> --- Smylers <[EMAIL PROTECTED]> wrote:
>
> > > child directory I'm fairly certain of. I am certain that more
> > > than one 'extra tests' directory is needed,
> >
> > Why are you certain of this? It seems far from obvious to me.
>
> for example:
>
> xt/smoke
>
> The latter
On 8/17/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
> 1. author (kwalitee, pod, etc)
> 2. gui
> 3. network
> 4. you must have an account/password on $external_service
> 5. postgres/mysql/whatever availability/setup/permissions
> 6. no modem attached to /dev/ttyS0
>
> Thus: "more t
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 compatib
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
--- chromatic <[EMAIL PROTECTED]> wrote:
> Which compatibility issues? I've used t/author/ for quite a while
> without any
> compatibility issues.
Because some people run "recursive" tests (what a bad name) by default
and descend into t/ subdirectories. As a result, they'd be running
author te
On 8/17/07, chromatic <[EMAIL PROTECTED]> 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
> > m
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?)
> >>
> >> (They
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 (ob
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 than the harness
> jus
Christopher H. Laco wrote:
> 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 t
Adriano Ferreira wrote:
> Testing some Author stuff would be rarer than having author tests. So
> maybe we could standardize on something like "t/author" and when other
> value is desirable, a key/value pair may be specified in META.yml (and
> in Makefile.PL/Build.PL).
>
> # META.yml
> ---
>
> #
On 8/17/07, brian d foy <[EMAIL PROTECTED]> wrote:
> In article
> <[EMAIL PROTECTED]>, Adriano
> Ferreira <[EMAIL PROTECTED]> wrote:
>
>
> > Testing some Author stuff would be rarer than having author tests. So
> > maybe we could standardize on something like "t/author" and when other
> > value is
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 a
In article
<[EMAIL PROTECTED]>, Adriano
Ferreira <[EMAIL PROTECTED]> wrote:
> Testing some Author stuff would be rarer than having author tests. So
> maybe we could standardize on something like "t/author" and when other
> value is desirable, a key/value pair may be specified in META.yml (and
> i
# from chromatic
# on Friday 17 August 2007 11:28 am:
>... sort of like I've been doing for at least one and probably two
> years now with Module::Build and my custom disttest action, which I
> know I've mentioned a few times now, which leads me to wonder why
> people so conveniently forget it eve
# from Michael G Schwern
# on Friday 17 August 2007 11:13 am:
>> # when something different is wanted
>> author_tests: t/developer
>
>Now you need a YAML parser to run tests, which may be fine.
But you also need to update all of the tools, which may not.
--Eric
--
But as soon as you hear the Do
On Friday 17 August 2007 12:52:54 Eric Wilhelm wrote:
> # from chromatic
> # on Friday 17 August 2007 11:28 am:
> >... sort of like I've been doing for at least one and probably two
> > years now with Module::Build and my custom disttest action, which I
> > know I've mentioned a few times now, whi
# from chromatic
# on Friday 17 August 2007 01:05 pm:
>On Friday 17 August 2007 12:52:54 Eric Wilhelm wrote:
>> 1. it doesn't play nicely with recursive tests[1]
>
>"It's okay to run everything in t/ recursively" is a heuristic. You
> can tell it's a heuristic because sometimes it's wrong.
Th
# from David Golden
# on Friday 17 August 2007 10:03 am:
>On 8/17/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
>> 1. author (kwalitee, pod, etc)
>> 2. gui
>> 3. network
>> 4. you must have an account/password on $external_service
>> 5. postgres/mysql/whatever availability/setup/permi
On Friday 17 August 2007 13:20:39 Eric Wilhelm wrote:
> >> 1. it doesn't play nicely with recursive tests[1]
> >"It's okay to run everything in t/ recursively" is a heuristic. You
> > can tell it's a heuristic because sometimes it's wrong.
> That's not what I meant by "doesn't play nicely".
# from chromatic
# on Friday 17 August 2007 01:57 pm:
>On Friday 17 August 2007 13:20:39 Eric Wilhelm wrote:
>> "my project cannot use recursive tests *and* have author-only tests
>> in t/author without jumping through hoops."
>How are you getting recursive tests by default anywhere?
I'm not get
Eric Wilhelm writes:
> # from Smylers
> # on Thursday 16 August 2007 11:40 pm:
>
> > > I am certain that more than one 'extra tests' directory is needed,
> >
> > Why are you certain of this?
>
> Because I already have a use for three 'profiles' in one project and I
> can name a few others from
# from Smylers
# on Friday 17 August 2007 03:13 pm:
>Eric Wilhelm writes:
>Why can't gui tests simply be in t/ and be skipped if the appropriate
>environment isn't available? That way all users who are in that
>particular environment run the tests, rather than only those who've
>discovered the xt
# from Adriano Ferreira
# on Friday 17 August 2007 11:49 am:
>The only drawback is redundant information: there are the tests and
>the list of tests. Keeping tests in "t/" with some fine way to
>discover what they are good for (according to Chris' idea) may be
>promising if not too magical.
I thi
29 matches
Mail list logo
