Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

jonasbn (1153)

  reversethis-{gro.napc} {ta} {nbsanoj}
AOL IM: BJonasN (Add Buddy, Send Message)

Perl Programmer located in Copenhagen, Denmark. Active member of Copenhagen Perl Mongers.

Author of:

  • Business::DK::CPR
  • Business::DK::CVR
  • Business::DK::PO
  • Business::OnlinePayment::CashCow
  • Date::Holidays
  • Date::Holidays::Abstract
  • Date::Holidays::Super
  • Date::Pregnancy
  • Games::Bingo
  • Games::Bingo::Bot
  • Games::Bingo::Print
  • Module::Info::File
  • Module::Template::Setup
  • Test::Timer

and maintainer of:

  • Tie::Tools
  • XML::Conf
  • Workflow

Journal of jonasbn (1153)

Saturday July 08, 2006
02:57 PM

Workflow, the road ahead

[ #30223 ]

Some of the things I added to the TODO when taking over this project was:

  • Write more POD, including a tutorial
  • Write more tests (we need better coverage)

I have with the latest releases applied some of the minor patches and fixed some of the easy bugs at the same time attempted to add tests to visualize the problems and give me an indication of when I had a working fix.

This added to the overall coverage and to the POD coverage aswell, but now awaits a few bigger things - and before jumping into these I would like to have better test coverage for the sake of regression test, I do not want to break anything, or at least not be able to find out what I broke.

So currently the POD coverage looks like the following (according to pod_cover):

  sub routines total : 135
  sub routines covered : 75
  sub routines uncovered: 60
  total coverage : 55.55%

hyperstation ~/develop/cvs-logicLAB/modules/workflow

When the POD is covered I also expect to have a better understanding of larger parts of the code and I will be able to write the unit-tests to get the overall coverage up to an acceptable level, where it will be useful prior to addressing the major issues:

  • Workflow::Factory inheritance (currently not working)
  • Dynamic configuration loading/changing

I myself have added the following things to the TODO list:

  • Change POD format to comply with Pod::Coverage (this is practically done, hence the report above
  • Add better handling of missing filename parameter in Workflow::Config::Perl
  • Add support for string based configuration a la XML::Simple
  • There are a few other minor things, please see the TODO file in the latest dist.

The Workflow module is quite marvellous and I am learning a lot as I go along - it is sad Chris Winters do not have the time to continue his work, but then again I have a great opportunity to get my hands on somebody else's code and Workflow is big, but still very self-contained, just the kind of task I like.

Workflow seems to have a small but very active community and I plan to strengthen this a bit, possibly with the following initiatives:

  • Mailinglist
  • Website with HTML documentation and more graphical content

Suggestions for other things are most welcome.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.