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.
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.
Using Test::PerlTidy, any file ending in .pl, .pm, .t or .PL will cause a test fail unless it is exactly as perltidy would like it to be.
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.
Test::File::ShareDir is some low level plumbing to enable a distribution to perform tests while consuming its own share directories in a manner similar to how they will be once installed.
Test::Version checks to ensure that all modules have a version defined, and that the version is valid.
The Test::WriteVariants module provides for the dynamic generation of tests in nested combinations of contexts.
This module tests that commands given particular arguments result in particular outputs by way of the exit status word, standard output, and standard error.
Test::RunValgind checks weather Valgrind does not detect errors (such as memory leaks) in an arbitrary binary executable.
This test module helps write unit tests which assert that the code under test reports metrics via Metrics::Any.
Testing code can involve making sure that files are created and deleted as expected. Doing this manually can be error prone, as it's easy to forget a file, or miss that some unexpected file was added. This module simplifies maintaining test directories by tracking their status as they are modified or tested with this API, making it simple to test both individual files, as well as to verify that there are no missing or unknown files.
This module was written to ensure that a META.yml file meets the specification.
This module performs various checks on a module's Regexp::Pattern patterns.
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.
Test::DistManifest provides a simple method of testing that a MANIFEST file matches its distribution.
Test::EOL lets you check for the presence of trailing whitespace and/or windows line endings in your perl code.
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 lets you check your module's namespaces for imported functions you might have forgotten to remove with namespace::autoclean or namespace::clean and are therefore available to be called as methods, which usually isn't want you want.
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 module contains a collection of acceptance tests for implementations of Future::IO.
This module was written to ensure that a META.json file meets the specification.
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.
This module provides a test that checks all dependencies have been installed properly.
This module exports three test functions and four diff-style functions.
Test::Manifest overrides the default test file order. Instead of running all of the t/*.t files in ASCII-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for the build system to do the right thing.