Thank you choroba, Bravo!! (you went from "choroba has never used --state" to figuring the answer out rather quickly ;-)
Update: Although it seems to be not quite true that "By appending t to the command line, you told prove to run all the tests in t/ together with the failed ones." ... apparently prove skips from the directory any test files that have already been run via failed.
Since I never rely on prove's looking for t/ by default it did not occur to me that the examples in the doc are showing complete commands.
I think --state would be more useful for me if it applied to individual tests within files (and within subtests even!) Maybe a plugin is called for.
The way forward always starts with a minimal test.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.