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 search send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
Loading this plugin causes your tests to fail if there any warnings while they run. Each warning generates a new failing test and the warning content is outputted via diag.
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.
Test::Portability::Files module is used to check the portability across operating systems of the names of the files present in the distribution of a module. The tests use the advices given in 'Files and Filesystems' in perlport. The author of a distribution can select which tests to execute.
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.
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.
Test::Class provides a simple way of creating classes and objects to test your code in an xUnit style.
Built using Test::Builder, it was designed to work with other Test::Builder based modules (Test::More, Test::Differences, Test::Exception, etc.).
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 Perl testing library focuses on testing and working with XPath expressions, most likely in the context of XML document processing.
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 provides a few convenience methods for testing exception based code. It is built with Test::Builder and plays happily with Test::More and friends.
This Perl module is intended to easily test network connectivity to non-local Internet resources before functional tests begin. If the sockets cannot connect to the specified hosts and ports, the exception is caught and reported, and the tests skipped.
Test::DistManifest provides a simple method of testing that a MANIFEST file matches its distribution.
The Mock::Config Perl module allows temporarily setting and overriding Config values, even for the readonly XSConfig implementation as used in cperl. It does not store the mocked overrides lexically, just dynamically.
This module provides the most commonly used testing functions, along with automatically turning on strict and warning and gives a bit more fine-grained control over test suites.
The Test::WriteVariants module provides for the dynamic generation of tests in nested combinations of contexts.
Test::Needs allows you to 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.
Tainted data is data that comes from an unsafe source, such as the command line, or, in the case of web apps, any GET or POST transactions. Read the perlsec man page for details on why tainted data is bad, and how to untaint the data.
When you're writing unit tests for code that deals with tainted data, you'll want to have a way to provide tainted data for your routines to handle, and easy ways to check and report on the taintedness of your data, in standard Test::More style.
This module performs various checks on a module's Regexp::Pattern patterns.
This module was written to ensure that a META.yml file meets the specification.
Test::More::UTF8 is a simple extension for the widely used Test::More module. By default, it will do a binmode on all of :utf8Test::Builder's output handles thus enabling the easy use flagged strings without warnings like "Wide character in print …"
This module tests that commands given particular arguments result in particular outputs by way of the exit status word, standard output, and standard error.
Check POD files for errors or warnings in a test file, using Pod::Simple to do the heavy lifting.
At some point or another, most programmers find they need to compare floating-point numbers for equality. The typical idiom is to test if the absolute value of the difference of the numbers is within a desired tolerance, usually called epsilon. This module provides such a function for use with Test::More.
This module allows you to deliberately hide modules from a program even though they are installed. This is mostly useful for testing modules that have a fallback when a certain dependency module is not installed.