Thanks to some sterling work by ehuelsmann, not least of which was badgering me to commit some code, Test::BDD::Cucumber now integrates directly into prove. This means you can run your feature files in parallel, and in a shuffled order more easily. This is a bit of a mouthful to achieve:
prove -s -j 5 -r --source Feature --feature-option extensions=.feature --ext=.feature examples/
and any suggestions on how to make…
I am messing around trying to fix the QIF files that Lloyds TSB CC statements are presented as, and needed to write XML.
XML::Writer seems like a reasonable solution, but I’m not OK with writing a static header by using 300 calls to $writer->startTag(‘blah’).
This seems a good job for the computer; specifically for a SAX parser which will happily parse non-balanced XML. Anyway, the result is:
my $writer = XML::Writer::Lazy->new( OUTPUT => 'self');
my $title = "My Title!";
<p>Pipe in literal XML</p>
$writer->startTag( "p", "class" => "simple" );
$writer->characters("Alongside the usual interface");
Which is considerably lazier, and allows you to intersperse actual XML::Writer commands with chunks of XML string and have it do largely the right thing.
Long-time Perlista hfb reports from a sadly regressive DEFCON:
I've released the second part of my series comparing Perl, Python and Ruby's testing ecosystems, on my testing-focussed blog
I've started a new series on my testing blog about the differences between Perl, Python, and Ruby's testing ecosystems and architectures. First article looking at the most basic assertions is done: