I just got back from JOIN (Jornadas de Informatica) 2005, a little student
run conference at the University of Minho in Portugal. Why this might be
of interest is its the same place and largely the same folks who will be
running YAPC::Europe.
http://natura.di.uminho.pt/join2005/out/news_en.html
On Thu, Feb 24, 2005 at 11:47:31AM -0600, Ken Williams wrote:
Better would be to snark it from ExtUtils::CBuilder, which has a
has_compiler() method.
How portable is this? I see there's some minimal VMS and OS/2 code in
there, will it work?
If so then the MakeMaker tests can just use
Michael G Schwern wrote:
I was asked to give something about testing to an audience of undergraduate
informatics students, largely Haskell and maybe some Java. What I finally
came up with is this:
http://www.pobox.com/~schwern/talks/Why_Test/
Liked the emphasis on version control. Had to learn
Test::Output 0.05 has been released.
The main difference in this version is a patch from chromatic (thank
you). His patch fixed a bug where all tests printed error diags even if
they passed. Additional tests were added to ensure that no output is
sent from diag in successful tests.
While
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
The main difference in this version is a patch from chromatic (thank
you). His patch fixed a bug where all tests printed error diags even
if they passed. Additional tests were added to ensure that no output
is sent from diag in
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
test results?
It still chokes on certain not uncommon constructs like threads.
Michael G Schwern wrote:
On Fri, Mar 04, 2005 at 04:27:07PM -0800, Ofer Nave wrote:
Random thought: Could Devel::Cover be automatically run against all
modules in CPAN, with ratings posted on cpan.org right next to the usual
test results?
It still chokes on certain not uncommon
On Fri, Mar 04, 2005 at 04:44:42PM -0800, Ofer Nave wrote:
Is it possible to tell quasi-reliably if the code in question uses
threads and skip it? On that note, is forking also problematic?
Not really. Anywhere within the test or any code called by the test might
use threads. Devel::Cover
Ofer Nave wrote:
Shawn Sorichetti wrote:
Test::Output 0.05 has been released.
Renaming thread since only the OP referred to Test::Output.
It occurs to me that the Test::* and ExtUtils::* modules should be the
first stop for the Phalanx project. :)
At least as originally proposed by project
At least as originally proposed by project leader Andy Lester, Phalanx
was supposed to focus on *non-core*,
Not exactly. I just figured it's easier for teams to submit tests back
to individual authors than back to Perl itself. Also, those patches
are more likely to get out into the
10 matches
Mail list logo
