QA Hackathon 2014

This year's QA hackathon was held last weekend in Lyon. 30 of the nicest and cleverest people I know met for four days with the common goal of improving Perl's quality with specific reference to testing and the toolchain. I was there too.

Google Code-In 2012

Could your module or project benefit from having someone

  • fix a specific bug
  • add a test for a specific feature
  • improve test coverage by 5%
  • write a tutorial
  • create a screencast for beginners
  • write an example program
  • create a homepage for the module

?

If so, you could be in luck. These are all potential tasks for students in this year's Google Code-In.

Following on from our success last year, The Perl Foundation is hoping to take part in the Google Code-In again this year. GCI is a program…

cpancover

I've started work on my Devel::Cover grant from TPF. If you are interested you can see my report for the first week at http://www.nntp.perl.org/group/perl.qa/2012/05/msg13184.html.

As a part of that work I have updated cpancover and moved it to a new home at http://cpancover.com.

cpancover is my project to provide coverage details for CPAN modules. Whilst useful in its own right, I also tend to use CPAN as my extended test suite for Devel::Cover. I was able to procu…

Vim report for Devel::Cover (Perl QA Hackathon) - part 2

At last week's QA Hackathon in Paris I put together a Vim report for Devel::Cover to show coverage information as Vim signs. See http://blogs.perl.org/users/paul_johnson/2012/03/vim-report-for-develcover-perl-qa-hackathon.html

Whilst nice, and somewhat useful, this was very much a proof of concept. It only worked for statement coverage, it wasn't particularly clever, nor was it particularly pretty.

I've just released Devel::Cover version 0.86 which solves a number of these problems. It shows all types of coverage data (that Devel::Cover knows about), it seems to be pretty u…

Vim report for Devel::Cover (Perl QA Hackathon)

Last night over dinner I had a discussion with Miyagawa about what Devel::Cover could steal from Ruby. He mentioned a Ruby backend which uses Vim signs to show coverage information.

So today I shamelessly stole it and produced a basic version for Devel::Cover.

Devel::Cover has more coverage criteria, so extra work will be required to provide this information, but the report seems useful for now. To use it run

$ cover -report vim

and then in vim:

:so cover_db/coverage.vim

I'd be happy to…