Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Perl 6 test suite
Perl6 Other

A bunch of tests for when is/isn't OK.

We leave the given/for/CATCH/CONTROL cases to the many existing tests.
latest commit 55c98f8c23
@jnthn jnthn authored
Failed to load latest commit information.
S01-perl-5-integration Use isa-ok instead of isa_ok
S02-lexical-conventions missing infix is now missing, not confused
S02-lists Use isa-ok instead of isa_ok
S02-literals Use isa-ok instead of isa_ok
S02-magicals Use isa-ok instead of isa_ok
S02-names-vars Use isa-ok instead of isa_ok
S02-names auto-unfudge.
S02-one-pass-parsing Remove any Pugs fudges
S02-packages Use isa-ok instead of isa_ok
S02-types tweaks for new non-flattening for loop
S03-binding Add test for RT #65900
S03-feeds lolly-proof uses of (;)
S03-junctions also test that listop forms are flattening
S03-metaops Use isa-ok instead of isa_ok
S03-operators Use isa-ok instead of isa_ok
S03-sequence test for /foo/ endpoint
S03-smartmatch check revised semantics for Whatever vs ~~
S04-blocks-and-statements Use isa-ok instead of isa_ok
S04-declarations Add test for RT #115916
S04-exception-handlers Add test for program-level handlers.
S04-exceptions Use isa-ok instead of isa_ok
S04-phasers Use isa-ok instead of isa_ok
S04-statement-modifiers Tests covering regression in given/for s.m.
S04-statement-parsing Use isa-ok instead of isa_ok
S04-statements A bunch of tests for when is/isn't OK.
S05-capture Use isa-ok instead of isa_ok
S05-grammar Use isa-ok instead of isa_ok
S05-interpolation Tests for RT #77152 (<&foo($arg)>).
S05-mass run unicode property pair tests on moar
S05-match Use isa-ok instead of isa_ok
S05-metachars Unfudge some more passing tests for Parrot
S05-metasyntax Use isa-ok instead of isa_ok
S05-modifier Use isa-ok instead of isa_ok
S05-nonstrings Remove any Pugs fudges
S05-substitution Use isa-ok instead of isa_ok
S05-syntactic-categories "use MONKEY_TYPING" -> "use MONKEY-TYPING"
S05-transliteration Unfudge now passing tests.
S06-advanced Use isa-ok instead of isa_ok
S06-currying Fudge failing test for RT 123498
S06-macros Unfudge all passing JVM specific todo'd tests
S06-multi Use isa-ok instead of isa_ok
S06-operator-overloading Use isa-ok instead of isa_ok
S06-other Skip rather than todo failing test on JVM
S06-routine-modifiers use _join where flattening is still desired
S06-signature Use isa-ok instead of isa_ok
S06-traits Tests for is copy trait on native args.
S07-iterators Use isa-ok instead of isa_ok
S09-autovivification Use isa-ok instead of isa_ok
S09-hashes Use isa-ok instead of isa_ok
S09-subscript Use isa-ok instead of isa_ok
S09-typed-arrays Add some more native int/num array tests
S10-packages Use isa-ok instead of isa_ok
S11-modules check that `require "ENOTTHERE"` does not segfault, RT #115626
S12-attributes Use isa-ok instead of isa_ok
S12-class Use isa-ok instead of isa_ok
S12-coercion Use isa-ok instead of isa_ok
S12-construction Use isa-ok instead of isa_ok
S12-enums Use isa-ok instead of isa_ok
S12-introspection Use isa-ok instead of isa_ok
S12-meta tweaks for new non-flattening for loop
S12-methods Use isa-ok instead of isa_ok
S12-subset Use isa-ok instead of isa_ok
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 Use isa-ok instead of isa_ok
S14-roles Use isa-ok instead of isa_ok
S14-traits eval => EVAL in S14 to S32
S15-nfg Fudge UTF-16 file/NFG tests.
S15-normalization Add generated normalization sanity tests.
S15-string-types Correct a .ord test, unfudge on rakudo.moar.
S15-unicode-information Tests for RT #124144 (uniname out of bounds).
S16-filehandles When you remove a test, adjust the count, duh!
S16-io Merge branch 'master' of git://github.com/perl6/roast
S16-unfiled remove references to "browser" os.
S17-channel Fix some Supply.for deprecation messages
S17-lowlevel Use isa-ok instead of isa_ok
S17-procasync Use isa-ok instead of isa_ok
S17-promise Use isa-ok instead of isa_ok
S17-scheduler Use isa-ok instead of isa_ok
S17-supply Test new Supply.rotor multiple gap functionality
S19-command-line-options Cope with test file having Windows newlines.
S19-command-line .exit is now .exitcode
S22-package-format Use isa-ok instead of isa_ok
S24-testing Use isa-ok instead of isa_ok
S26-documentation Use isa-ok instead of isa_ok
S28-named-variables Remove any Pugs fudges
S29-any Increase/Decrease -> Less/More migration
S29-context Use isa-ok instead of isa_ok
S29-conversions Fix test description; unfudge for rakudo.moar.
S29-os Add test for RT #104794
S29-type Remove any Pugs fudges
S32-array Use isa-ok instead of isa_ok
S32-basics Add some AT-POS & friends tests on native arrays
S32-container /._join/.flat.join/
S32-exceptions Fix two tests now EVAL'd in scope of caller
S32-hash Use isa-ok instead of isa_ok
S32-io Use isa-ok instead of isa_ok
S32-list .unique and .squish don't flatten
S32-num Use isa-ok instead of isa_ok
S32-scalar Use isa-ok instead of isa_ok
S32-str Use isa-ok instead of isa_ok
S32-temporal Use isa-ok instead of isa_ok
S32-trig Remove any Pugs fudges
integration Unfudge test for RT #122306.
packages Use isa-ok instead of isa_ok
rosettacode tweak OUT override
t Add more tests for fudging
.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 Make sure we will fudge kebabcased test functions
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.