App::Prove::State::SQLite

Ovid publiustemp-tapx at yahoo.com
Thu Mar 6 13:37:59 UTC 2008


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.

Cheers,
Ovid

--
Buy the book  - http://www.oreilly.com/catalog/perlhks/
Perl and CGI  - http://users.easystreet.com/ovid/cgi_course/
Personal blog - http://publius-ovidius.livejournal.com/
Tech blog     - http://use.perl.org/~Ovid/journal/


More information about the tapx-dev mailing list