[perl #43339] [TODO] config/inter/ops.pm: Write unit tests

2007-10-27 Thread James Keenan via RT
> > My recommedation is that we do here what we did in inter::pmc, viz., > > eliminate the prompting code and change this class from inter::ops to > > auto::ops. > > > > Any objection? > > None whatsoever, have at it. > r22530: Module refactored and renamed; corresponding test file renamed. C

Re: [perl #43339] [TODO] config/inter/ops.pm: Write unit tests

2007-10-27 Thread Will Coleda
On Oct 27, 2007, at 10:52 AM, James Keenan via RT wrote: In http://rt.perl.org/rt3/Public/Bug/Display.html?id=43172, we discussed the fact that in configuration step class inter::pmc, the code for prompting the user to select among pmc's was, in effect, turned off because we weren't sure that

[perl #43339] [TODO] config/inter/ops.pm: Write unit tests

2007-10-27 Thread James Keenan via RT
In http://rt.perl.org/rt3/Public/Bug/Display.html?id=43172, we discussed the fact that in configuration step class inter::pmc, the code for prompting the user to select among pmc's was, in effect, turned off because we weren't sure that it was advisable, at this point in time, to permit users to ma

[perl #43339] [TODO] config/inter/ops.pm: Write unit tests

2007-10-21 Thread James Keenan via RT
File holding framework for writing tests for this configuration step was committed to trunk Oct 21 2007 in r22362. Tests do not yet provide high coverage due to obstacles in testing runstep(). You are encouraged to poke around and add tests.

[perl #43339] [TODO] config/inter/ops.pm: Write unit tests

2007-06-22 Thread via RT
# New Ticket Created by James Keenan # Please include the string: [perl #43339] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=43339 > Write unit tests for config/inter/ops.pm, the module whose functionality executes Parro