gain.
>
> What are some suggestions to make sure that passing TODO tests get
> regular attention?
>
Make a TODO that passes all subtests a failure? Not sure how to go about
it, but it sure would get your attention :)…
Bye,
--
Pedro Melo
@pedromelo
http://www.simplicidade.or
at the time
> Devel::Cover decided whether or not to collect coverage data for the LOGOP the
> last COP seen was indicating that coverage shouldn't be collected. The
> solution was to check PL_curcop at appropriate times.
This alone made my week. :)
Thanks!
--
Pedro Melo
@pe
but mostly for grouping. I don't care
at all for the separate plan for subtests.
If tomorrow the sub subtest in Test::More became:
sub subtest {
diag("Testing ".shift);
shift->();
}
I probably would not notice :)
Bye,
--
Pedro Melo
@pedromelo
http://www.simplicidade.or
; AFARI CPAN.pm looks into other mirrors once it doesn't find a module,
> which would happen for local modules only in CPAN::Mini.
Never tried this either, but maybe start with an empty local CPAN and
CPAN::Inject into that. Then use that one as the first mirror on your
CPAN.pm con
t I don't know how
> you would do this with git.
The same way. Create a separate repository with the shared
dependencies, and include it on your projects as a submodule (git
version of svn externals).
Bye,
--
Pedro Melo
http://www.simplicidade.org/
xmpp:m...@simplicidade.org
mailto:m...@simplicidade.org
Hi,
On Fri, Oct 29, 2010 at 6:24 PM, Graham TerMarsch wrote:
> On October 28, 2010, Pedro Melo wrote:
>> All the process got me thinking about Test::Builder. I spent a couple
>> of hours tonight trying to see how would I output JUnit with TB2. I
>> tried to write a For
some kind soul could take a little bit of time
to point me in the right direction (maybe there is a TAP2 tree
somewhere?), I could go and look and try to make use of my hacked
TB2::Formatter::JUnit.
Thanks,
--
Pedro Melo
http://www.simplicidade.org/
xmpp:m...@simplicidade.org
mailto:m...@simplicidade.org