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.
  • Not Sure (Score:2, Informative)

    by chromatic (983) on 2003.04.02 11:41 (#18683) Homepage Journal

    Allowing known failures is a very slippery slope. Like bugs, test failures should be an exceptional thing.

    If you're doing XP, your engineering tasks should be short enough that you don't have to leave them overnight. If they're that large or that complex or things are going that poorly one afternoon, split them or just start over in the morning. The further you stray from a checkin, the less feedback the rest of the team has from your code.

    If you're not doing (or aren't trying to do) full-blown XP, it's not so bad. Still, the idea of leaving one test failing and work undone overnight really bugs me. More artificially-flavored fruit-like drink, anyone?

    • You could check in everything *but* the failing test. Leave that on your hard drive.
      • Great minds -- that occurred to me right after posting. :) Since getting started is the hardest part, fixing a simple, failing test might have jump-start the day.