Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by larard (1407) on 2010.06.17 10:44 (#72085)

    I always find you stories of TDD inspiring, almost to the point that I begin to write tests ;)

    But what I'm waiting for is tote! Or tote for perl 5 perhaps;) http://use.perl.org/~masak/journal/39639 [perl.org]

    • Oh, nice, someone who is actually waiting for tote. :)

      Now that I know that's the case, I will re-prioritize it to arrive sooner. The short story of my discoveries after the original post is that one shouldn't over-design tote; it mostly needs to be a loop that runs the tests on any changes, and has sensible rules for what constitutes "regression" and "progress". Having it do more (for example the double loop suggested in the original post) tends to be more of an obstacle than an actual help.

      Using tote works

      • Count me among those who’d like to see tote exist as a project.

        (Btw: elsewhere, someone I mentioned tote to suggested adding to it something like unit testing achievements [github.com], for unparalleled addictiveness.)

        • Ooh! Yes, that's certainly worth remembering. Many of these can probably be added quite easily.

          (I let out an involuntary snort when reading the first one: "A suite of at least 50 tests takes less than a second to run." I wish. On my laptop, a 2.4 GHz Intel Core 2 Duo, it never takes less that 1.1 seconds to run a program consisting purely of an empty for statement doing 50 iterations. There are still improvements to be made on the speed front.)