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.
This module provides routines for testing the exit status, standard output and standard error of external commands.
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::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.
Test::Roo provides composable, reusable tests with roles.
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.
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 adds a test to your Perl distribution which checks for pod coverage of all appropriate files.
Test::File provides a collection of test utilities for file attributes.
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::Output provides a simple interface for testing output sent to STDOUT or STDERR. A number of different utilities are included to try and be as flexible as possible to the tester.
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.).
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 some drop-in replacements for the string comparison functions of Test::More, but which are more suitable when you test against long strings.
Test::Tester allows testing of test modules based on Test::Builder with a minimum of effort.
In situations where you have deep trees of classes, there is a common situation in which you test a module 4 or 5 subclasses down, which should follow the correct behaviour of not just the subclass, but of all the parent classes.
This should be done to ensure that the implementation of a subclass has not somehow ``broken'' the object's behaviour in a more general sense.
Test::Object is a testing package designed to allow you to easily test what you believe is a valid object against the expected behaviour of all of the classes in its inheritance tree in one single call.
This module creates a Fake ShareDir for your modules for testing.
This package provides a rich set of tools, plugins, bundles, etc built upon the Test2 testing library.
This module exports three test functions and four diff-style functions.
Test::SharedFork is a utility module for Test::Builder. It makes fork(2) safe to use in test cases.
Test::YAML is a subclass of Test::Base with YAML specific support.
Test::Requires checks to see if the module can be loaded. If this fails, then rather than failing tests this skips all tests.
Test::Base gives a way to trivially write your own test framework base class. It concentrates on offering reusable data driven patterns, so that you can write tests with a minimum of code.
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.