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.
  • Sounds like a great idea! On the graph, a use-case which may or may not be valid TDD: I try to write a test for a class which does not yet exist, so the build fails on the left hand side, but instead of going hackety hack, I'm taken back to write test.
    • That's right. My current view of this is that you should be taken back to "write test", even though you'll be writing a stubbed class thereafter. (Maybe the framework can be smart enough to recognize that you need to write the stubbed class, and tell you as much. But nominally, you'll still end up in "write test".) Why? Because in order to proceed to "hack, hack", you need to actually provide a new test which fails.

      That's just my current understanding of the vaporware. Alternative interpretations are welcom