Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Test::RunValgind checks weather Valgrind does not detect errors (such as memory leaks) in an arbitrary binary executable.
Test::Class::Most provides some more convenience when using Test::Class.
Test::Inter is another framework for writing test scripts, which offer the ability to access specific tests in a reasonably interactive fashion, primarily for debugging purposes. Much of the syntax is loosely inspired by Test::More.
This module provides a few convenience methods for testing warning based code.
This module tests that commands given particular arguments result in particular outputs by way of the exit status word, standard output, and standard error.
When used in a test script Test::Distribution goes through all the modules in your distribution, checks their POD, checks that they compile successfully and checks that they all define a $VERSION. In addition, this module performs a number of tests on the distribution itself. It checks that the distributed files match the SIGNATURE file, if that file exists. It checks that the distribution is not missing any core description files. It also checks that the complete set of pre-requisite packages are listed in the Makefile.PL file.
This module provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends.
Test::File provides a collection of test utilities for file attributes.
Fennec ties together several testing related modules and enhances their functionality in ways you don't get loading them individually. Fennec::Lite takes a minimalist approach to do for Fennec what Mouse does for Moose.
Test::Simple contains basic utilities for writing tests.
Test::File::Contents provides functions for testing the contents of files.
Test::Requires checks to see if the module can be loaded. If this fails, then rather than failing tests this skips all tests.
This Perl testing library focuses on testing and working with XPath expressions, most likely in the context of XML document processing.
This module exports three test functions and four diff-style functions.
Test::Filename provides functions to convert all path separators automatically.
Test::Memory::Cycle is built on top of Devel::Cycle to give you an easy way to check for these circular references.
use Test::Memory::Cycle; my $object = new MyObject; # Do stuff with the object. memory_cycle_ok( $object );
This module is a collection of tests useful for dealing with UTF-8 strings in Perl. This module 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.
Test::Deep compares two structures by going through each level, ensuring that the values match, that arrays and hashes have the same elements and that references are blessed into the correct class. It also handles circular data structures without getting caught in an infinite loop.
This module is intended to be used as a drop-in replacement for Test::NoWarnings. It also adds an extra test, but runs this test before done_testing calculates the test count, rather than after. It does this by hooking into done_testing as well as via an END block. You can declare a plan, or not, and things will still Just Work.
This module is primarily (but not exclusively) for use in test scripts: A block eval configurable and extensible but by default trapping STDOUT, STDERR, warnings, exceptions, would-be exit codes, and return values from boxed blocks of test code.
Test::Version checks to ensure that all modules have a version defined, and that the version is valid.
Test::Fatal is an alternative to the popular Test::Exception. It does much less, but should allow greater flexibility in testing exception-throwing code with about the same amount of typing.
Testing code which forks is problematic because each test has a number associated with it. Coordinating the test number amongst the parent and child processes is complicated. Test::Fork provides a function to smooth over the complications.
The intent of the Test::Script module is to provide a series of basic tests for 80% of the testing you will need to do for scripts in the script (or bin as is also commonly used) paths of your Perl distribution.