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.
  • If you want a real rush, get into test-driven development. Write a test, watch it fail, then write the code to make it pass. It's a weird but enjoyable experience to realize "That's all the code I needed to write!"

    • Actually, that's what I'm aiming for. That, or something very like it. I just need to set things up so I can cycle from design to test to code to design to test to code more easily (i.e., all from within my editor and my browser rather than switching and shifting gears ad nauseam).

      The individual tests in the modules I've been working on tend to be pretty long, though. Maybe Test::Inline can be convinced to help with that (e.g., let me specify a 'preamble' of setup code that all tests can use). Sometimes cranking up a new .t file is a breath of fresh air.

      I've looked at Mock::Object a couple of times now and the idea of it is very appealing, but I need to mull it over before I grok it. Much mulling may be required.

      My current project will depend on a custom object model [perl.org], which is what I'm developing now. Once I'd gotten a whiff of design-and-test-and-code-all-at-once, it didn't take me long to realize I could use the idea of worlds of objects to set up different test environments: I can create simple worlds for simple tests now and grow into bigger worlds over time.