Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Perl 6 test suite
Perl6 Other
Failed to load latest commit information.
S01-perl-5-integration Use 'Perl5' as consistent name for EVAL and use :from
S02-lexical-conventions Add basic test for $=finish
S02-lists Use isa-ok instead of isa_ok
S02-literals Update test now we have a typed exception here.
S02-magicals Extra, missing, stress test for &?ROUTINE.
S02-names-vars Test for RT #74756.
S02-names Change (and move) test for RT #98854
S02-one-pass-parsing Remove any Pugs fudges
S02-packages s/lives_ok/lives-ok/g
S02-types Add Index as a valid type
S03-binding kebab case skip-rest
S03-feeds Remove all superstitious "done"s
S03-junctions Refer to existing ticket
S03-metaops Add todo test for RT#118791
S03-operators Revert "benign prep for ~~ going chained -> structural"
S03-sequence Remove all superstitious "done"s
S03-smartmatch Revert "benign prep for ~~ going chained -> structural"
S04-blocks-and-statements Correct and unfudge test.
S04-declarations Remove tests out of line with current design.
S04-exception-handlers kebab case skip-rest
S04-exceptions tests for some enhancements to die/fail
S04-phasers Test for RT #125480.
S04-statement-modifiers s/eval_dies_ok/eval-dies-ok/g
S04-statement-parsing s/lives_ok/lives-ok/g
S04-statements tests for some enhancements to die/fail
S05-capture Remove three tests with wrong assumptions about capturing
S05-grammar Don't be case-sensitive in text test.
S05-interpolation Change two skipped tests to todo
S05-mass reduce the scope of some fudges.
S05-match RT #125345, test (non-)capturing and cursor pos
S05-metachars Tests for RT #72440.
S05-metasyntax reduce the scope of some fudges.
S05-modifier kebab case skip-rest
S05-nonstrings Remove any Pugs fudges
S05-substitution Remove all superstitious "done"s
S05-syntactic-categories s/eval_lives_ok/eval-lives-ok/g
S05-transliteration s/lives_ok/lives-ok/g
S06-advanced Adapt tests to new CallFrame.gist method
S06-currying Test needs to be skipped on moar as well.
S06-macros Tweaks for PR#475 (new Exception code.)
S06-multi Add new RT number to new tests.
S06-operator-overloading Correct test, unfudge for rakudo (RT #124980)
S06-other Further RT #125376 tests.
S06-routine-modifiers s/eval_lives_ok/eval-lives-ok/g
S06-signature Test for RT #125670.
S06-traits Use unique ticket numer for RT #124640
S07-iterators Remove all superstitious "done"s
S09-autovivification s/lives_ok/lives-ok/g
S09-hashes Add test for RT #125352
S09-subscript s/eval_lives_ok/eval-lives-ok/g
S09-typed-arrays Fudge a new test that does not work on JVM
S10-packages Fix test to not produce a sink warning.
S11-modules Test for RT #125715.
S12-attributes Fix copy-pasta in test; lucasb++.
S12-class Fix test description
S12-coercion reduce the scope of some fudges.
S12-construction Remove all superstitious "done"s
S12-enums Remove tests out of line with current design.
S12-introspection Add tests covering RT #80694.
S12-meta Remove all superstitious "done"s
S12-methods RT #125661: Error reporting for private methods in a try
S12-subset s/lives_ok/lives-ok/g
S12-traits s/lives_ok/lives-ok/g
S13-overloading fixed appended RT number to be within quoted string
S13-syntax s/lives_ok/lives-ok/g
S13-type-casting Use isa-ok instead of isa_ok
S14-roles Test RT #73390, RT #100468, RT #88750, RT #76450.
S14-traits Test submethods and traits interaction.
S15-nfg Tweak to make the test "harder".
S15-normalization Add generated normalization sanity tests.
S15-string-types .graphs is gone, remove tests and comments
S15-unicode-information fixed appended RT number to be within quoted string
S16-filehandles Add some tests for RT#113100
S16-io fix various deprecations as spotted by RAKUDO_DEPRECATIONS_FATAL=1
S16-unfiled fixed appended RT number to be within quoted string
S17-channel fix minor typo
S17-lowlevel reduce the scope of some fudges.
S17-procasync Pick a program that exists for Windows.
S17-promise Test for RT #125346.
S17-scheduler s/dies_ok/dies-ok/g
S17-supply Remove () now that start is no longer a sub
S19-command-line-options Per design specs, -E isn't in perl6.
S19-command-line Fix test which relied on exact match of error message on JVM.
S22-package-format s/dies_ok/dies-ok/g
S24-testing kebab case skip-rest
S26-documentation reduce the scope of some fudges.
S28-named-variables s/lives_ok/lives-ok/g
S29-any s/dies_ok/dies-ok/g
S29-context s/evalfile/EVALFILE/, add lexical visibility test.
S29-conversions Remove all superstitious "done"s
S29-os Add tests for RT #115390
S32-array Add test for RT#119913
S32-basics Fix thinkos and typos; Mouq++.
S32-container Remove all superstitious "done"s
S32-exceptions Test for RT #125675.
S32-hash Tests for hash slice adverb exception handling
S32-io Fix deprecation in test.
S32-list todo => skip on some very dubious tests.
S32-num update to new sign(Int) behavior
S32-scalar Remove all superstitious "done"s
S32-str Minimal test changes for rindex(--> Index)
S32-temporal RT #125683: Validate minutes in timezone
S32-trig s/eval_dies_ok/eval-dies-ok/g
integration Test we get concise error on last statement sink.
packages Test for RT #125715.
rosettacode tweak OUT override
t Add more tests for fudging
.gitignore Remove any Pugs fudges
LICENSE Add Artistic License 2
README kebab case skip-rest
TODO Add a note about RTs.
fudge Make fudge aware of some more functions from packages/Test/
fudgeall Added quotes in case fudge path has spaces. (Tested on Linux and Win3…
test_summary avoid unnecessary differences in output

README

	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:

    #?MYSPECIALVAR: [NUM] VERB ARGS
    #!MYSPECIALVAR: [NUM] VERB ARGS

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.