Perl 6 test suite
Perl6 Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
S01-perl-5-integration Un-TODO passing test Sep 19, 2016
S02-lexical-conventions [TODO FUDGE] Unspace with sigiless terms Jul 12, 2016
S02-lists Test ()[0] returns Nil Oct 28, 2016
S02-literals “smart” → “curly” (related to RT #130260) Dec 4, 2016
S02-magicals Unfudge tests for JVM Oct 6, 2016
S02-names-vars Unfudge some tests for rakudo-j Jul 16, 2016
S02-names Add use v6 where appropriate Feb 24, 2016
S02-one-pass-parsing Fix incorrect exit code in test Aug 19, 2016
S02-packages prefer RT #ticket Nov 1, 2015
S02-types Test issues with Inf term Dec 3, 2016
S03-binding Unfudge now passing test Aug 19, 2016
S03-feeds Remove dubious test Sep 19, 2015
S03-junctions Fix copy/pasta error in test description Nov 14, 2016
S03-metaops Fix typo in comment Nov 15, 2016
S03-operators gcd operator with zeros Nov 13, 2016
S03-sequence Change range indexing semantic tweaks. Dec 1, 2015
S03-smartmatch Unfudge tests for JVM Oct 6, 2016
S04-blocks-and-statements Fudge newly added tests for JVM Sep 27, 2016
S04-declarations Replace deprecated is_approx with is-approx Oct 19, 2016
S04-exception-handlers Cover CX::Emit and CX::Done. Oct 31, 2016
S04-exceptions Add more Exceptions::JSON tests Oct 10, 2016
S04-phasers Fudge some newly added tests for JVM Nov 25, 2016
S04-statement-modifiers prefer RT #ticket Nov 1, 2015
S04-statement-parsing s/lives_ok/lives-ok/g May 20, 2015
S04-statements Unfudge passing test for JVM Nov 29, 2016
S05-capture Test equality and identity of Match objects Nov 20, 2016
S05-grammar Test for RT #130081. Nov 16, 2016
S05-interpolation Make sure that we only have one "use lib" Mar 11, 2016
S05-mass Unfudge tests that require Java 8 (unicode 6.1) Oct 8, 2016
S05-match Add test for smartmatching finite vs infinite Seq Oct 31, 2016
S05-metachars Test for RT #122891. Nov 10, 2015
S05-metasyntax Test bare \b and \B in regexes are forbidden Dec 4, 2016
S05-modifier Add test for $/ not being set inside for { } issue Oct 31, 2016
S05-nonstrings Remove any Pugs fudges Jul 11, 2014
S05-substitution Test .subst() with no args does not infiniloop Nov 26, 2016
S05-syntactic-categories Expect Exception, not X::AdHoc. Nov 12, 2015
S05-transliteration Adverbs on Cool.trans work the same as on Str.trans Sep 12, 2016
S06-advanced Also cover use of callframe in a hot loop. Oct 19, 2016
S06-currying Make sure that we only have one "use lib" Mar 11, 2016
S06-macros Fix test where eval-lives-ok didn't get right context Dec 10, 2015
S06-multi Make sure where-blocked multi is prior to non-where-blocked multi (#155) Sep 6, 2016
S06-operator-overloading Replace deprecated is_approx with is-approx Oct 19, 2016
S06-other Revert "Temporarily fudge enum MAIN tests for release" Nov 19, 2016
S06-parameters Expect Exception, not X::AdHoc. Nov 12, 2015
S06-routine-modifiers Test for RT #127540. Jul 21, 2016
S06-signature Test Signature.gist does not strip typeless anon scalar sigils Dec 4, 2016
S06-traits Test error when assigning to ro var has the name Nov 30, 2016
S07-hyperrace .hyper preserves order Sep 10, 2016
S07-iterators Test Iterator.skip-at-least-pull-one Nov 10, 2016
S07-slip slip tests Oct 1, 2015
S09-autovivification Fix creation of nested arrays in S09-autovivification/autoincrement.t Aug 28, 2015
S09-hashes Add test for RT #111498 Apr 11, 2016
S09-multidim Revert "Fudge test for X::Assignment::ToShaped for JVM" Nov 30, 2016
S09-subscript Unfudge tests for RT #128341 (rakudo-j) Nov 13, 2016
S09-typed-arrays Unfudge test for antipairs + native arrays on JVM Nov 13, 2016
S10-packages Need a little rest to pass on OSX Sep 17, 2016
S11-compunit Use $*EXECUTABLE instead of 'perl6', fudge for JVM Dec 17, 2015
S11-modules Another test for nested packages Oct 26, 2016
S11-repository Fix "no writable path" found in curli-install.t Dec 28, 2015
S12-attributes Fudge tests for RT #128031 on JVM Apr 30, 2016
S12-class Test augment of a nested class. Oct 26, 2016
S12-coercion Use ticket number RT #126524 for fudging Oct 30, 2016
S12-construction Initial tests for submethod TWEAK Nov 7, 2016
S12-enums [coverage] Cover all routines in Oct 3, 2016
S12-introspection Add test for RT #127059 Oct 30, 2016
S12-meta Make sure that we only have one "use lib" Mar 11, 2016
S12-methods Add test for slightly unconventional attributive binding Nov 28, 2016
S12-subset Add test description Oct 20, 2016
S12-traits Replace remaining eval-dies-ok with throws-like Oct 1, 2015
S13-overloading Expect Exception, not X::AdHoc. Nov 12, 2015
S13-syntax s/lives_ok/lives-ok/g May 20, 2015
S13-type-casting Use isa-ok instead of isa_ok Apr 26, 2015
S14-roles Unfudge tests on JVM Oct 6, 2016
S14-traits Revert "Fudge RT #129375 for rakudo.jvm" Sep 28, 2016
S15-literals Conversion of 'No' chars to numeric is not supported Jul 7, 2016
S15-nfg update charrange tests for RT #128550 Aug 13, 2016
S15-normalization Add use v6 where appropriate Feb 24, 2016
S15-string-types Add use v6 where appropriate Feb 24, 2016
S15-unicode-information Test for Unicode 9 character support. Sep 28, 2016
S16-filehandles Test IO::Handle.printf Nov 27, 2016
S16-io Picking first file from /proc/1 for eof testing Sep 23, 2016
S16-unfiled fixed appended RT number to be within quoted string May 5, 2015
S17-channel Fudge newly added tests for JVM Nov 3, 2016
S17-lowlevel Correct test that did unprotected array writes. Aug 10, 2016
S17-procasync Cover data-loss fix to Proc::Async. Nov 23, 2016
S17-promise Test to cover RT #130064. Nov 16, 2016
S17-scheduler Adapt tests because of 2a635cd96279ace1c5d3d6d687 Dec 6, 2015
S17-supply Test .emit works as a method Dec 4, 2016
S19-command-line-options Fudge some tests in preparation to add files to Aug 19, 2016
S19-command-line Use ticket number RT #126524 for fudging Oct 30, 2016
S22-package-format S22-package-format/local.t: use $*SPEC.catdir() to account for backsl… Dec 21, 2015
S24-testing Replace deprecated is_approx with is-approx Oct 19, 2016
S26-documentation Add missing plan Oct 14, 2016
S28-named-variables Prepare for removal of @*INC Nov 29, 2015
S29-any [coverage] Add tests for Any.[nl-out|print-nl] Sep 20, 2016
S29-context Revert "Fudge test for RT #130170 for JVM" Nov 26, 2016
S29-conversions test chrs on list of numifiable strings Nov 11, 2016
S29-os Use ticket number RT #126524 for fudging Oct 30, 2016
S32-array Resolves #164: tests callable args on splice (#176) Oct 20, 2016
S32-basics Fudge failing test for JVM Nov 18, 2016
S32-container Test infix:<~>(Blob:D) Nov 25, 2016
S32-exceptions Test to cover RT #129921. Oct 26, 2016
S32-hash [coverage] Cover Map.clone Oct 13, 2016
S32-io Unfudge test for $fh.get after $ on JVM Nov 26, 2016
S32-list Add initial tests for deepmap (#161) (#181) Nov 10, 2016
S32-num Fix test which breaks on 32 bit systems (#185) Nov 28, 2016
S32-scalar Unfudge tests on JVM Oct 6, 2016
S32-str Test for .at, not .pos in parse-base exception tests Dec 3, 2016
S32-temporal Test DateTime.hh-mm-ss Nov 8, 2016
S32-trig Replace deprecated is_approx with is-approx Oct 19, 2016
integration Make test for output of backtrace less specific Nov 18, 2016
packages Add is-deeply-junction to Test::Util Nov 23, 2016
rosettacode Fix Windows line ending workarounds. Nov 3, 2015
t Add more tests for fudging Apr 20, 2015
.gitignore ignore .precomp folders Dec 11, 2015 Move "contributing" doc to its own file Nov 14, 2016
LICENSE Add Artistic License 2 Nov 5, 2013 Move "contributing" doc to its own file Nov 14, 2016
TODO Add a note about RTs. Jul 20, 2014
fudge Replace deprecated is_approx with is-approx Oct 19, 2016
fudgeall Added quotes in case fudge path has spaces. (Tested on Linux and Win3… Jun 18, 2008
test_summary avoid unnecessary differences in output Mar 4, 2015

The Official Perl 6 Test Suite

The purpose of the test suite is to validate implementations that wish to be known as a conforming Perl 6 implementation.



Please consider this test suite to be the bleeding edge of Perl 6 development. New tests, tests for experimental new features, etc., will live on this 'master' branch. Once a specification is cut, a branch will be created for that version of the spec, e.g., 6.c for Christmas.

As they develop, different implementations will certainly be in different states of readiness with respect to the test suite, so in order for the various implementations to track their progress independently, we've established a mechanism for fudging the tests in a kind of failsoft fashion. To pass a test officially, an implementation must be able to run a test file unmodified, but an implementation may (temporarily) skip tests or mark them as "todo" via the fudging mechanism, which is implemented via the fudge preprocessor. Individual implementations are not allowed to modify the actual test code, but may insert line comments before each actual test (or block of tests) that changes how those tests are to be treated for this platform. The fudge preprocessor pays attention only to the comments that belong to the current implementation and ignores all the rest. If your implementation is named "rakudo" then your special comment lines look like:

#?rakudo: [NUM] VERB ARGS

(The colon is optional.)

The optional NUM says how many statements or blocks to apply the verb to. (If not supplied, a value of 1 is assumed). A statement is arbitrarily defined as one or more lines starting with a test call and ending in a semicolon (with an optional comment).

VERBs include:

skip "reason"   # skip test entirely
eval "reason"   # eval the test because it doesn't parse yet
try "reason"    # try the test because it throws exception
todo "reason"   # mark "todo" because "not ok" is expected
emit code       # insert code (such as "skip-rest();") inline

All fudged tests return an exit code of 1 by default, so the test harness will mark it as "dubious" even if all the tests supposedly pass.

You may also negate the test:

#!rakudo [NUM] VERB ARGS

This will apply the verb on any system that isn't rakudo.

Sometimes environment variables distinguish syntactic or semantic variants, so you may apply a verb depending on the presence or absence of such a setting:


The environment variable must be uppercase.

There is also the following directive which modifies the test count of the next construct:

#?DOES count

The count may be an expression as long as any variables referenced in the expression are in scope at the location fudge eventually inserts a "skip()" call.

When applied to a subsequent sub definition, fudge registers the sub name as doing that many tests when called. Note, however, that any skipping is done at the point of the call, not within the subroutine, so the count may not refer to any parameter of the sub.

When you run the fudge preprocessor, if it decides the test needs fudging, it returns the new fudged filename; otherwise it returns the original filename. (Generally you don't run fudge directly, but your test harness runs the fudgeall program for you; see below.) If there is already a fudged program in the directory that is newer than the unfudged version, fudge just returns the fudged version without regenerating it. If the fudged version is older, it removes it and then decides anew whether to regenerate it based on the internal fudge comments.

The fudgeall program may be called to process all the needed fudging for a particular implementation:

$ fudgeall rakudo */*.t */*/*.t

Program fudgeall will use the fudge program to translate any fudged files to a new file where the extension is not *.t but instead is *.rakudo to indicate the implementation dependency. It also returns the fudged list of filenames to run, where unfudged tests are just passed through unchanged as *.t. Each test comes through as either fudged or not, but never both. The test harness then runs the selected test files as it normally would (it shouldn't care whether they are named *.t or *.rakudo).

In cases where the current working directory makes a difference, the tests assume that the working directory is the root of the test suite, so that the relative path to itself is t/spec/S\d\d-$section/$filename.

Environment Variables


Some tests rely on a process to complete in a certain amount of time. If you're running on a slowish computer, try setting ROAST_TIMING_SCALE to a larger value that will be used as a multiplier for the time to wait. We don't wait for too long a time by default so as to make the roast run faster. Defaults to 1.