Results 3,331–3,340 of 5,623 for /devel/.(0.003 seconds)
Handy UTF-8 tests
Test::utf8 is a collection of tests useful for dealing with utf8 strings in
Perl. It has two types of tests: The validity tests check if a string is valid
and not corrupt, whereas the characteristics tests will check that string has a
given set of characteristics.
Damerau Levenshtein edit distance
Text::Levenshtein::Damerau returns the true Damerau Levenshtein edit distance of
strings with adjacent transpositions. Useful for fuzzy matching, DNA variation
metrics, and fraud detection.
Text::Levenshtein::Damerau defaults to using Pure Perl
Text::Levenshtein::Damerau::PP, but has an XS addon
Text::Levenshtein::Damerau::XS for massive speed imrovements. Works correctly
with utf8 if backend supports it; known to work with
Text::Levenshtein::Damerau::PP and Text::Levenshtein::Damerau::XS.
Test required module is really used and vice versa
Test dependency between module and META.yml.
This module reads META.yml and get build_requires and requires.
It compares required module is really used and used module is
really required.
XS implementation of the Levenshtein edit distance
This is a port of Josh Goldberg's Text::LevenshteinXS
An XS implementation of the Levenshtein edit distance
Strip leading whitespace from here-docs
Strips leading whitespace from here-docs
More tools for testing Moose packages
This package contains a number of additional tests that can be employed
against Moose classes/roles. It is intended to replace L<Test::Moose> in your
tests, and reexports any tests that it has and we do not, yet.
Enhancing Test::More for UTF-8-based projects
Test::More::UTF8 is an enhancement of Test::More for UTF8-based projects.
Perl extension for most commonly needed test functions and features
Most commonly needed test functions and features.
Perl extension to fill test names from caller line
Test::Name::FromLine is test utility that fills test names from its
file. Just use this module in test and this module fill test names to
all test except named one.
Skip tests when modules not available
Skip test scripts if modules are not available. The requested modules will be
loaded, and optionally have their versions checked. If the module is missing,
the test script will be skipped. Modules that are found but fail to compile will
exit with an error rather than skip.
If used in a subtest, the remainder of the subtest will be skipped.
Skipping will work even if some tests have already been run, or if a plan has
been declared.
Versions are checked via a $module->VERSION($wanted_version) call. Versions must
be provided in a format that will be accepted. No extra processing is done on
them.
If perl is used as a module, the version is checked against the running perl
version ($]). The version can be specified as a number, dotted-decimal string,
v-string, or version object.
If the RELEASE_TESTING environment variable is set, the tests will fail rather
than skip. Subtests will be aborted, but the test script will continue running
after that point.