Re: Best practices for TODO test management?

Hi Mark,

I know this isn't exactly what you want, but a long time ago I added a --directives switch to 'prove' to help with this. If you do this:

    prove -lr --directives t/

'prove' will *not* run in verbose mode, except for any tests with directives (TODO and SKIP).
 
It's not perfect, but at least it will make the TODO tests stand out (they're also colored differently if you're using colors).

Cheers,
Ovid
--
Twitter - http://twitter.com/OvidPerl/
Buy my book - http://bit.ly/beginning_perl
Buy my other book - http://www.oreilly.com/catalog/perlhks/
Live and work overseas - http://www.overseas-exile.com/


>________________________________
> From: Mark Stosberg <[email protected]>
>To: perl-qa <[email protected]> 
>Sent: Wednesday, 27 February 2013, 15:06
>Subject: Best practices for TODO test management?
> 
>
>We have a large test suite with 20,000+ tests in it, and a number of
>passing TODO tests in it.
>
>Our problem is that once a test is marked as TODO, it falls off our
>radar, and we are unlikely to notice it again.
>
>What are some suggestions to make sure that passing TODO tests get
>regular attention?
>
>I was hoping that 'prove' might have a flag to treat passing-TODOs as
>failures, but Id didn't see one.
>
>I would prefer not to write a custom harness... this seems like a
>feature that would be of general interest.
>
>In case this context matters-- our tests are regularly through Jenkins,
>so our TAP is getting converted to JUnit. We also run tests from the
>command line with prove regularly as well.
>
>Thanks!
>
>   Mark
>
>
>