[perl #45601] [RFC] Plans and notes for the unified testing branch

[Will Coleda via RT]

On Tue Nov 27 17:01:27 2007, scratchcomputing at gmail.com wrote:
> # 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 regardless (e.g. calling 
> Test::Harness::runtests() will no longer pickup on your custom straps 
> package.)
> 
> >I wonder whether any major obstacles have surfaced and whether it
> > makes sense to merge the changes in 'unified_testing' with 'trunk'
> > again.
> 
> As far as the harness is concerned, yes.  Using the TAP::Harness API 
is 
> preferable.
> 
> If the parrot-land changes aren't 100% (e.g. unifying the way in which 
> tests expect to be called), the old harness will still need to deal 
> with the fact that the Test::Harness internals have changed and Straps 
> is no longer available through that API.
> 
> --Eric
> 

Can we get a update on this over at https://trac.parrot.org/parrot/wiki/BranchDescriptions ?

(And then close out this ticket?)

-- 
Will "Coke" Coleda