On Do. 20. Sep. 2007, 13:03:31, [EMAIL PROTECTED] wrote:
> Goals:
>
> Completely unified testing. The ability to run tests and aggregate
> their
> results regardless of how the test is implemented, (perl, parrot, hll,
> etc.)
> HTML Reports should function much as we have now, but with the
> add
# from Bernhard Schmalhofer via RT
# on Tuesday 27 November 2007 16:22:
>after the release of Test::Harness 3.03 I'm wondering about the status
>of the 'unified_testing' branch.
Test::Harness::Straps doesn't exist in the new Test::Harness, so trunk
would need to catchup with that issue regardles
# from James Keenan via RT
# on Friday 21 September 2007 13:44:
>On Thu Sep 20 13:03:31 2007, [EMAIL PROTECTED] wrote:
>>http://perlsix.org/svn/parrot/view/branches/unified_testing/BRANCH_TODO
>>...
>> 5) Add processing of the output of Configure --test.
>
>When I began working on writing tests fo
On Thu Sep 20 13:03:31 2007, [EMAIL PROTECTED] wrote:
> http://perlsix.org/svn/parrot/view/branches/unified_testing/BRANCH_TODO
>
>
> Goals:
>
> Completely unified testing.
[snip]
> 5) Add processing of the output of Configure --test.
>
When I began working on writing tests for the Perl 5 co
> 2) Write a coding standard test to make sure that t/* tests call out a
> location
>independent parrot/interpreter.
Just for your information: you might be most of the way there on this
part of the proposal. We already have a similar test for #!perl
shebang lines, see:
lib/Perl/Critic/Poli
# New Ticket Created by Colin Kuskie
# Please include the string: [perl #45601]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=45601 >
http://perlsix.org/svn/parrot/view/branches/unified_testing/BRANCH_TODO
Goals:
Comple
