Test::More

Test::More is a unit testing module for Perl. Created and maintained by Michael G Schwern with help from Barrie Slaymaker, Tony Bowden, chromatic, Fergal Daly and perl-qa.

Test::More
Original author(s)Michael G Schwern
Developer(s)Chad 'Exodist' Granum
Initial releaseApril, 2001
Written inPerl
Operating systemCross-platform
Available inEnglish
TypeUnit testing module
LicenseDual-licensed - Artistic License and GPL
Websitehttp://search.cpan.org/~exodist/Test-Simple-1.302096/lib/Test/More.pm

Test::More is the most popular Perl testing module, as of this 2010 about 80% of all CPAN distributions made use of it.[1]

History

Introduced in 2001 to replace Test.pm, Test::More simplified and re-energized the culture of testing in Perl leading to an explosion of new testing modules and a strongly test driven community.

In January–March 2014 Michael Schwern transferred ownership of Test::More and related modules to Chad 'Exodist' Granum.[2] On May 10, 2016 Exodist released version 1.302015[3][4] which included a complete refactor and partial rewrite of the internals. The new version includes major API updates and introduced several enhanced features. Extreme care was taken to preserve backwards compatibility for third party tools.

Functionality

Test::More is not a framework but can be used in concert with other testing libraries via a shared Test::Builder object. As a result, Test::More provides the baseline testing functions leaving other libraries to implement more specific and sophisticated functionality. This removes what would otherwise be a development bottleneck and allows a rich ecosystem of specialized niche testing functions.

Test::More is not a complete testing framework. Rather, test programs written with Test::More output their results as TAP which can then either be interpreted by a human, or more usually run through a TAP parser such as Test::Harness. It is this separation between test program and test result interpreter via a common protocol which allows Perl programmers to develop so many different testing modules and use them in combination. Additionally, the TAP output can be stored and reinterpreted later providing a historical record of test results.

gollark: I would probably use netcat.
gollark: Oh, very, but only in a chroot-type thing, not baremetal.
gollark: Yes, that is one of the very specific phones.
gollark: So probably a chrootish thing.
gollark: You can't except on very specific phones.

References


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.