Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Perl 6 test suite
Failed to load latest commit information.
S01-perl-5-integration This test isn't run by rakudo.
S02-lexical-conventions unfudge some items
S02-lists yes, the test is correct, since Zen should decont
S02-literals tweak tests for latest bogus listop errors
S02-magicals Unfudge now passing tests
S02-names-vars unfudge some items
S02-names Add test for RT #123696
S02-one-pass-parsing Remove any Pugs fudges
S02-packages fix tests for lookup of our-variables in a class
S02-types Check for the 3 new PairMap related classes
S03-binding Add test for RT #65900
S03-feeds lolly-proof uses of (;)
S03-junctions so() and not() are now well-behaved functions
S03-metaops Add test for RT #123178
S03-operators tweak tests for latest bogus listop errors
S03-sequence make sure unicode ellipis works for sequence op
S03-smartmatch remove inadvertent shape declarations from tests
S04-blocks-and-statements Fix typos.
S04-declarations Unfudge two passing tests for rakudo.jvm
S04-exception-handlers Add test for program-level handlers.
S04-exceptions unfudge some items
S04-phasers Add test for RT #122765
S04-statement-modifiers Unfudge some more passing tests for Parrot
S04-statement-parsing Remove any Pugs fudges
S04-statements Unfudge passing test.
S05-capture Add test for RT #77570
S05-grammar Fix typos.
S05-interpolation Add test for RT#100232 which might be fixed at this point
S05-mass unfudge some items
S05-match Add test for RT #83508
S05-metachars Unfudge some more passing tests for Parrot
S05-metasyntax Match.gist doesn't end with a newline anymore
S05-modifier unfudge some items
S05-nonstrings Remove any Pugs fudges
S05-substitution quoters now lexically overridable by terms/subs
S05-syntactic-categories [t/spec] add 'use MONKEY_TYPING' where appropriate
S05-transliteration Unfudge now passing test
S06-advanced unfudge some items
S06-currying Fudge failing test for RT 123498
S06-macros Adapt test for RT #122746
S06-multi Remove any Pugs fudges
S06-operator-overloading check new add_categorical errors
S06-other some rakudo fudging
S06-routine-modifiers Add tests for native rw sub semantics.
S06-signature some rakudo fudging
S06-traits Tests for is copy trait on native args.
S07-iterators s/done_testing/done/ as per recent S24 changes
S09-autovivification Test for autovivification on multidim access
S09-hashes Add test for RT #118037
S09-subscript Unfudge test for RT#123594.
S09-typed-arrays Test for RT#66892.
S10-packages Make sure tests fail for the right reason
S11-modules Add test for RT #84280
S12-attributes unfudge some items
S12-class Unfudge test for RT #67784
S12-coercion Update fudging after fixing an optimizer bug.
S12-construction Add a test for RT #77200
S12-enums Add test for RT #123114
S12-introspection Test .^can interaction with submethods.
S12-meta Fudge 6 tests for JVM (todo); skip all tests for Parrot
S12-methods class.*bar returns Parcel, not Nil
S12-subset Fudge (skip) failing test for rakudo.parrot (RT #123234)
S12-traits Remove any Pugs fudges
S13-overloading Take the full argument list when overriding (...) for Type(...)
S13-syntax movie sub/hash syntax
S13-type-casting RT #72834
S14-roles Unfudge another passing test.
S14-traits eval => EVAL in S14 to S32
S15-string-types some rakudo fudging
S15-unicode-information tag with RTs
S16-filehandles Fix typos.
S16-io Update test now that Pair has a nicer gist method.
S16-unfiled remove references to "browser" os.
S17-channel Test Channel.closed without .receive
S17-lowlevel Unfudge: this seems stable now, even under load
S17-procasync some rakudo fudging
S17-promise unfudge two now-passing tests, lizmat++
S17-scheduler Make sure we don't die on empty arrays
S17-supply Fix deprecated .sleep call
S19-command-line-options Cope with test file having Windows newlines.
S19-command-line Avoid test failure in S19-command-line/repl.t on parrot
S22-package-format Unfudge now passing precomp test, jnthn++
S24-testing Remove superfluous trailing '1;'s and trailing whitespace
S28-named-variables Remove any Pugs fudges
S29-any Increase/Decrease -> Less/More migration
S29-context Remove any Pugs fudges
S29-conversions Remove any Pugs fudges
S29-os use $*EXECUTABLE in run() tests
S29-type Remove any Pugs fudges
S32-array Add test for RT #116897
S32-basics use standard "NYI" text
S32-container Remove any Pugs fudges
S32-exceptions track error message changes
S32-hash antipairs and inversions
S32-io Replace deprecated .directory by .dirname
S32-list Add test for RT #120620
S32-num explicit digits should produce trailing 0s
S32-scalar supress a couple of warnings
S32-str Unfudge now passing substr-rw() tests
S32-temporal Unfudge.
S32-trig Remove any Pugs fudges
integration some rakudo fudging
packages Add missing file for test for RT #84280
rosettacode tweak OUT override
.gitignore Remove any Pugs fudges
LICENSE Add Artistic License 2
README document new fudge directives, negated and envvar
TODO Add a note about RTs.
fudge teach fudge to know about envvars
fudgeall Added quotes in case fudge path has spaces. (Tested on Linux and Win3…
test_summary avoid unnecessary differences in output


	The Official Perl 6 Test Suite (someday...)

This is the Official Perl 6 test suite. It evolved out of the pugs
test suite, and is now maintained in a separate repository.

Its purpose is to validate implementations that wish to be known
as a conforming Perl 6 implementation. 

Please consider this test suite to be the result
of an ongoing negotiation: since many of these tests are inspired
by seeing how the various prototype implementations are screwed up
(or even more likely, how the design of Perl 6 is screwed up), this
test suite should be considered a work in progress until one or more
of the implementations gets close to passing the entire test suite,
at which point we will freeze version 6.0 of the test suite, and any
implementation that passes it can then call itself Perl 6.

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 platform and ignores all the rest.  If your
platform is named "humpty" then your special comment lines look like:

    #?humpty: [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 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:

    #!humpty: [NUM] VERB ARGS

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

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 environement 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, 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 platform:

    fudgeall humpty */*.t */*/*.t

will use the "fudge" program to translate any fudged files to a new
file where the extension is not *.t but instead is *.humpty to indicate
the platform 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 *.humpty).

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.
Something went wrong with that request. Please try again.