I'm excited to see that the Phalanx project is happening.
On the website I see this unfiled item:
"Use Devel::Cover and gconv".
One way that seems useful to use Devel::Cover is to have an automated coverage
testing system that would test the 100 module periodically.
All the phalanx page, an ex
On Sun, Oct 12, 2003 at 01:08:39PM +, Mark Stosberg wrote:
> A second sticking point could be that code is OS-specific, so it's not ever going
> to get testing by just one build machine.
And also, in the case of things like Class::DBI, have database specific
code in them, that is tested, but c
I was under the impression (I think I read it somewhere) that when
running "make test" if there is a test.pl file and a set of tests
in t/*.t only the former (test.pl) will run an the t/ directory
will be skipped.
I have just checked it and it seems to be not true.
That is, both test.pl and t/*.
On Sun, Oct 12, 2003 at 01:08:39PM +, Mark Stosberg wrote:
> I'm excited to see that the Phalanx project is happening.
>
> On the website I see this unfiled item:
>
> "Use Devel::Cover and gconv".
>
> One way that seems useful to use Devel::Cover is to have an automated coverage
> testing s
On Sun, Oct 12, 2003 at 06:28:52PM +0200, Gabor Szabo wrote:
> That is, both test.pl and t/*.t were executed.
AFAIK its always been this way. DBI relies on it.
--
Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/
It should indeed be said that notwithstanding the fact t
We've got a couple new hoplites out there, so check out the status page.
http://qa.perl.org/phalanx/status.html
Also, Paul Johnson has some slick stuff on CPAN module coverage that
should be interesting for new hoplites to take a look at, to see
which modules are covered least. Percentage asid
