Tag Archives: testing

The Annotated Lancaster Consensus

By dagolden | Published: April 19, 2013

The official Lancaster Consensus document is on Github. This blog post is an annotated review of it. The Lancaster Consensus At the first Perl QA Hackathon in 2008 in Oslo, a number of QA and toolchain authors, maintainers and experts came together to agree on some common standards and practices. This became known as "The […]

Posted in cpan, perl programming, toolchain | Also tagged , , , , | Comments closed

Perl QA hackathon 2013 wrapup

By dagolden | Published: April 19, 2013

I've been back from the Perl QA 2013 hackathon for a few days and I'm probably overdue to write about the trip. I'm intimidated by last years writeup — I must have been feeling a lot peppier on the plane a year ago. I've also been busying writing up the notes from the "Lancaster Consensus" […]

Posted in cpan, perl programming, toolchain | Also tagged , , , , | Comments closed

No more copy and paste: How to refactor tests with roles

By dagolden | Published: March 18, 2013

Raise your hand if you've ever cut and paste a huge chunk of code — or even a whole file — for testing. I have. And I feel guilty, because I know the DRY mantra: "Don't repeat yourself!" But somehow, rules we follow for our application code, we forget for our test code. Here's a […]

Posted in perl programming | Also tagged , , | Comments closed

Stop Pod tests before they stop you!

By dagolden | Published: March 16, 2013

Have you ever installed a CPAN module with a big dependency chain and had installation fail somewhere in the middle? Have you ever investigated and found the failure was due to Test::Pod or Test::Pod::Coverage? AAARRRGGGHHH! I hate that! Pod tests are release tests and shouldn't be inflicted on end users. But some authors got hooked […]

Posted in hacks, perl programming | Also tagged , , , | Comments closed

Alternative to Test::NoWarnings

By dagolden | Published: February 25, 2013

The Test::NoWarnings module is very helpful for detecting subtle errors in your code. Unfortunately, by default, it does its reporting in an END block, which doesn't play nicely with Test::More's done_testing() function, which I use a lot. There has been an open ticket since 2009 and nothing has been done. There is a workaround, but […]

Posted in perl programming, toolchain | Also tagged , , | Comments closed