t/ - The Parrot Virtual Machine Test Suite
This directory contains the official Parrot Virtual Machine test suite.
For details on how tests are written see the documentation in docs/tests.pod https://github.com/parrot/parrot/blob/master/docs/tests.pod. For status of the testing effort, see t/TESTS_STATUS.pod https://github.com/parrot/parrot/blob/master/t/TESTS_STATUS.pod.
The script 'harness' actually runs the test suite.
To run the normal Parrot test suite tests:
To run only the core test suite (intented to be used after
The run the full test suite, which is equivalent to "make test" under various runcores as well as coding standard tests:
To run just the coding standard tests:
To create code coverage reports from the Parrot test suite:
which requires the Devel::Cover Perl 5 module.
To submit "smoke" reports, you will need to install the TAP::Harness::Archive and LWP::UserAgent CPAN modules, and then type:
The report will then be visible on Smolder: http://smolder.parrot.org/app/projects/smoke_reports/1
If you only want to submit results of the core test suite to Smolder:
Below is a list of subdirs along with a short description of what is tested in there.
Run all the tests for all HLLs and libraries. Useful before and after merges to detect regressions in projects using Parrot.
Tests the coding conventions for Parrot source code.
Tests for compilers in Parrot.
Tests for the Perl modules in our configuration subsystem.
Tests that run before a distribution is released. Can be run with:
Tests for the completeness and sanity of the documentation.
Tests for dynamic (loadable at run-time) opcode libraries.
Tests for dynamic PMCs.
Tests to check whether the examples are still working. Can be run with:
Test Parrot modules that ship with core. Can be run with:
Tests for the functionality supporting the creation of MANIFEST and related files. Can be run with:
Tests Parrot Byte Code.
Tests for object oriented features of Parrot. Can be run with
Tests for Parrot opcodes. Can be run with
Tests for the Perl 5 modules used for configuration, building and testing of Parrot. Can be run with:
Tests for the functionality supporting Parrot's test harnesses.
Tests for Parrot PMCs. Can be run with
Tests of configuration system run after configuration has completed.
Tests for the command line options of the 'parrot' executable. Can be run with:
Tests written in C, mostly for the Embed/Extend subsystems. Can be run with
Tests for the steps in the Parrot configuration process.
Stress testing. Make Parrot sweat.
Tests for tools useful to Parrot core and HLL developers
Copyright (C) 2005-2011, Parrot Foundation.