The "PerlUnit" unit testing framework

If you don't know what a unit testing framework is or why you would want one, the links below will fill you in.

If you want a unit testing framework for perl, the details are in the project summary page (SSL). Here are some shortcuts to the important bits:

• Grab the current release from the SourceForge download area or from CPAN, where you can also read the POD.
• There is also the doc/ directory of the master branch, which includes a class diagram.
• We have two mailing lists, with archives:
  • perlunit-devel (low volume discussion)
  • perlunit-users (this list is quiet, if not silent)
  There are also some web-based forums but we've mostly abandoned them because we don't like the user interface.
• The code now lives in a Git repository. This was initialised from a curated cvs2git (v2.3.0) import of the CVS repository, and will carry future development of the code and this web page.

  git clone git://perlunit.git.sourceforge.net/gitroot/perlunit/perlunit

  [ Browse | Git native | project access instructions | generic SourceForge instructions | SSH fingerprints ]

  master

  The PerlUnit source code, which was addressed in CVS as Test-Unit or src/Test-Unit

  website

  Contains the website http://perlunit.sourceforge.net/, which was addressed in CVS as www.

  cvs/*

  Branches and tags representing the corresponding cvs2git imports.

  attic/*

  For posterity.

• Browse the CVS repository to see the old state of our files. A quick outline of what was there:

  src/Test-Unit

  This is the source for the distributed package.

  src/Test-Unit-0.06

  src/UnitTests

  src/XUnit-0.01

  src/api

  Old layouts of the project, everything is in the Attic. Ignore.

  src/junit3.2

  src/tools

  This is project history - what Brian used to start the project.

  www/

  Contains the website http://perlunit.sourceforge.net/, no released files or source.

  The CVS repository will remain up for a while, for the benefit of those who need to cvs diff their existing working copies, but will receive no more work.

FAQ

Or more honestly, questions I imagine may be asked.

Is this project dead?

The code can never die because it is available under the Artistic / GPL dual licence. SourceForge has shown good long-term reliability for keeping version control repositories intact and available.

So is the project alive?

Not very. It has been sleeping for a long time and currently has failing tests in the latest release.

Does anybody use it?

As recently as 2011, users have piped up to ask for help. Some of them have large codebases to maintain.

Is it on Github?

Yes. You are welcome to fork from mca-wtsi/perlunit but that is not the "official" repository.

Links related to PerlUnit aka. Test-Unit

Automated software testing is a large and growing area. These links may help you start your investigations.

Distribution, CPAN, other bug trackers

• The CPAN Testers make regular reports for Test-Unit.
• rt.cpan.org search for open Test-Unit bugs.
• The CPANTS report is a good game, but take the results with a pinch of salt! (Oct 2005)

About unit testing

• http://www.xProgramming.com/, Extreme Programming site
• http://JUnit.sourceforge.net/, Java unit testing framework from which Perlunit was cloned
• http://c2.com/cgi/wiki?PerlUnit, A forest of data at the Wiki Wiki Web

Other projects which support PerlUnit

• Test::Unit::Runner::XML, reports are in the same format as those produced by Ant's JUnit task.
• GTestRunner aka. Test::Unit::GTestRunner, a Gtk+ TestRunner GUI for Test::Unit.

Other projects for testing in Perl

These are the "standard" testing modules,

• Test::Simple, includes Test::More and Test::Builder
• Test::Harness

There are more,

• Test::Class (includes a good "SEE ALSO" list)
• Test::C2FIT
• Test::SimpleUnit

...many more.