App::Prove::State::SQLite

[Andy Armstrong]

On 6 Mar 2008, at 13:37, Ovid wrote:
> Here's the basic problem:
>
> We have a long-running test suite (80 minutes down to 12 minutes back
> up to 19 minutes) and as part of our test suite maintenance strategy,
> we wanted to capture test suite behavior over time.
>
> My first thought was to check in the .prove file to source control:
>
> $ svn status
> C      .prove
>
> OK, that's not going to work.  It's constantly generating conflicts  
> and
> while we have workarounds, at the end of the day, trying to shoehorn
> this need into source control is a bad fit.
>
> It think that an optional SQLite interface would be a great idea.  We
> could start storing test data over time, possibly see who's running  
> the
> tests ($< and $>) and basically capturing all information that
> TAP::Parser tracks.  If we had proper Devel::Cover integration, we
> could even possibly capture coverage results.
>
> If anyone has any ideas or suggestions, I'd love to hear 'em.


A plugin? Yes, +1 to the idea. I guess that App::Prove::State will  
need a little attention to make it a bit more general purpose.

-- 
Andy Armstrong, Hexten