Categories
Posts in this category
- A shiny perl6.org site
- Creating an entry point for newcomers
- Sprixel, a 6 compiler powered by JavaScript
- Another perl6.org iteration
- Blackjack and Perl 6
- Why I commit Crud to the Perl 6 Test Suite
- Report from the Perl 6 Hackathon in Copenhagen
- Custom operators in Rakudo
- Defined Behaviour with Undefined Values
- Dissecting the "Starry obfu"
- Perl 6: Failing Softly with Unthrown Exceptions
- The first Perl 6 module on CPAN
- Google Summer of Code Mentor Recap
- Building a Huffman Tree With Rakudo
- Immutable Sigils and Context
- Is Perl 6 really Perl?
- Perl 6: Lost in Wonderland
- Lots of momentum in the Perl 6 community
- Musing and the future of feather and the Pugs repository
- Musings on Rakudo's spectest chart
- My first executable from Perl 6
- Trying to implement new operators - failed
- Let's build an object
- Perl 6 is optimized for fun
- How to get a parse tree for a Perl 6 Program
- Perl 6 in 2009
- Perl 6 ticket life cycle
- The Perl 6 Advent Calendar
- How to Plot a Segment of a Circle with SVG
- Publicity for Perl 6
- Rakudo architectural overview
- Rakudo Rocks
- Rakudo "star" announced
- Rakudo's rough edges
- Rats and other pets
- Releasing Rakudo made easy
- Set Phasers to Stun!
- Starry Perl 6 obfu
- Recent Perl 6 Developments August 2008
- Strings and Buffers
- Subroutines vs. Methods - Differences and Commonalities
- A SVG plotting adventure
- A Syntax Highlighter for Perl 6
- Test Suite Reorganization: How to move tests
- The Happiness of Design Convergence
- Perl 6 Tidings from September and October 2008
- Perl 6 Tidings for November 2008
- Perl 6 Tidings from December 2008
- Perl 6 Tidings from January 2009
- Perl 6 Tidings from February 2009
- Perl 6 Tidings from March 2009
- Perl 6 Tidings from April 2009
- Perl 6 Tidings from May 2009
- Perl 6 Tidings from May 2009 (second iteration)
- Perl 6 Tidings from June 2009
- Perl 6 Tidings from August 2009
- Perl 6 Tidings from October 2009
- Timeline for a syntax change in Perl 6
- Visualizing match trees
- We write a Perl 6 book for you
- When we reach 100% we did something wrong
- Where Rakudo Lives Now
- Why was the Perl 6 Advent Calendar such a Success?
- What you can write in Perl 6 today
- Why you don't need the Y combinator in Perl 6
Wed, 15 Jul 2009
Musings on Rakudo's spectest chart
Permanent link
In an attempt to track progress in a measurable way, the Rakudo people count the number of passing tests each night (ok, they don't do that manually :-) and write that into a CSV file.
The next step wasn't far: generate a chart from it, put it on a website, and tell everybody about it. Here's a snapshot:

Old news so far, as an eager Perl 6 follower you surely know that already, nothing new here. But the other day somebody asked me why the green (PASS) and the grey (number of spectests available) seem to be parallel.
My first reaction was "no, they aren't parallel" because the big jumps don't happen at the same time, but still there are large areas where they do seem to grow roughly at the same rate. So what's up?
As far as I can tell there are two mechanism at work here. The first one accounts for much of the past behaviour: tests were moved from the old part of the pugs test suite to the official test suite (where they are counted towards the grey line), and at the same time people also tried to get it to run under Rakudo - mostly successfully, as the green line shows.
Now most test files are actually moved to the official Perl 6 test suite, there are less than 200 tests left to move (as opposed to 17k already moved), and this mechanism is drained.
The second mechanism is that as soon as Rakudo implements a cool new feature, we realize that we need more tests for it, and people write more tests for it. (It's rather hard to write tests for language feature that doesn't run yet. "test first" is a nice idea, but it only works to some extent in reality). Also people explore the new features, find bugs, and bug tickets are only closed if there are tests for them, so even more spec tests that coincide with passing Rakudo tests.
Comments / Trackbacks:
Trackback URL:
/blog-en/perl-6/musings-on-spectest-chart.trackback
Chris wrote
Awesome
"there are less than 200 tests left to moved!"
I for one am excited to start to see the gap between grey and green shrink. It was a long time in coming. Great work.
Carl Mäsak wrote
Gap may shrink, but it's not necessarily exciting
The grey tests becoming fewer does not mean that Perl 6 will be finished, unfortunately. Instead, it means that the massive implementation effort that we know as Rakudo will finally have caught up with the massive spectesting effort, which began in 2005 with Pugs.
Put simply, it'll mean we will have run out of tests. Come help write spectests!
Gabor Szabo wrote
counting tests
<i>the Rakudo people count the number of passing tests each night </i>
Now I understand why does it take so long to implement Perl 6 ;-)
Write a comment
The comments on this blog post have been disabled; the comment form below will not work.