App::Prove::State Questions

[Ovid]

I'm trying to improve the interface to App::Prove::State.  My short term goal is to create App::Prove::State::SQLite to allow people to store test suite information over time.

This raises some questions about App::Prove::State internals.

Issues.

1.   There's a DESTROY method.  This saves the state even if I kill the test suite.  This can throw long term test suite results off, but I can mark a test suite as 'incomplete' to get around this.

2.  There's a 'last_result' key.  This is true if the test program failed or had problems (such as passing TODO tests).  I'd like to split that key.

3.  Of course, I intend to extend the keys to capture tests run, tests failed and so on.

4.  Tracking reorganization of the test suite seems problematic.  If people rename or move test programs, this can throw results off, but we currently have no way of uniquely identifying a test program (much less an individual test).

Am I likely to break anything?  I don't know if anyone is really using the state syntax.

Comments/suggestions welcome.

Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6