Ovid wrote:
> - Original Message
>> From: chromatic
>
>> Add diagnostics to TODO tests and let your test harness do what it's
>> supposed
>> to do. Shoving yet more optional behavior in the test process continues to
>> violate the reasons for having separate test processes and TAP an
# from Ovid
# on Tuesday 14 July 2009 03:33:
>> Fork/branch Test::Builder and make it work yourself. When it's ready
>> and usable, ask Schwern to evaluate, improve and merge.
>>
>> Code = Conversation. :)
>
>I know. I've thought about that, but truth be told, I'm really
> getting burnt out with
On Tue, Jul 14, 2009 at 5:43 AM, Ovid wrote:
> We have no diagnostics. We've never had diagnostics (the ad-hoc things
> going to STDERR don't count because they can't be synched or reliably
> parsed). Thus, I can't add diagnostics to the TODO tests until Schwern puts
> diagnostics in Test::Builde
On Tuesday 14 July 2009 02:43:44 Ovid wrote:
> Thus, I'm trying to think of a way of solving my problem now, not at some
> hypothetical date in the future.
Next option: write your own test harness which dies when it encounters a bonus
test. This should take you less than an afternoon.
If that
On Tue, Jul 14, 2009 at 03:33:29AM -0700, Ovid wrote:
> I know. I've thought about that, but truth be told, I'm really getting burnt
> out with the Perl community right now. Lots of people are being rude,
> thinking that being "right" is all they need to justify being arrogant and
> it's sapp
- Original Message
> From: Salve J Nilsen
>
> Fork/branch Test::Builder and make it work yourself. When it's ready and
> usable,
> ask Schwern to evaluate, improve and merge.
>
> Code = Conversation. :)
I know. I've thought about that, but truth be told, I'm really getting burnt
o
Ovid said:
- Original Message
From: chromatic
Add diagnostics to TODO tests and let your test harness do what
it's supposed to do. Shoving yet more optional behavior in the
test process continues to violate the reasons for having separate
test processes and TAP analyzers.
We ha
- Original Message
> From: chromatic
> Add diagnostics to TODO tests and let your test harness do what it's supposed
> to do. Shoving yet more optional behavior in the test process continues to
> violate the reasons for having separate test processes and TAP analyzers.
We have no di
