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.
Parachute is a simple-to-use and extensible testing framework. In Parachute, things are organised as a bunch of named tests within a package. Each test can contain a bunch of test forms that make up its body.
KAPUTT is a test framework for Common Lisp that focuses on the following features:
KAPUTT is simple, it only defines three abstractions testcase, assertion and protocol and does not add any artefact on the backtrace when errors occur.
KAPUTT is extensible, it is possible to add problem-specific assertions to make test code more informative.
KAPUTT fits well interactive development.
This is a unit-testing framework for Common Lisp.
Eos was a unit testing library for Common Lisp. It began as a fork of FiveAM; however, FiveAM development has continued, while that of Eos has not. Thus, Eos is now deprecated in favor of FiveAM.
CLUnit2 is a Common Lisp unit testing framework. It is designed to be easy to use so that you can quickly start testing.
CLUnit is a Common Lisp unit testing framework. It is designed to be easy to use so that you can quickly start testing. CLUnit provides a rich set of features aimed at improving your unit testing experience.
A Common Lisp test framework that treasures your failures, logical continuation of Stefil. It focuses on interactive debugging.
The XLUnit package is a toolkit for building test suites. It is based on the XPTest package by Craig Brozensky and the JUnit package by Kent Beck.
LISP-UNIT2 is a Common Lisp library that supports unit testing in the style of JUnit for Java. It is a new version of the lisp-unit library written by Chris Riesbeck.
This is a small testing framework for Common Lisp. The entire API consists of: test, is, signals, finishes, run, suite and setf suite.
ptester is a portable testing framework based on Franz's tester module.
CLUnit2 is a Common Lisp unit testing framework. It is designed to be easy to use so that you can quickly start testing.
Try is a library for unit testing with equal support for interactive and non-interactive workflows. Tests are functions, and almost everything else is a condition, whose types feature prominently in parameterization.
KAPUTT is a test framework for Common Lisp that focuses on the following features:
KAPUTT is simple, it only defines three abstractions testcase, assertion and protocol and does not add any artefact on the backtrace when errors occur.
KAPUTT is extensible, it is possible to add problem-specific assertions to make test code more informative.
KAPUTT fits well interactive development.
This small library provides a way to replace the actual implementation of either regular or generic functions with mocks.
ptester is a portable testing framework based on Franz's tester module.
RT provides a framework for writing regression test suites.
This package provides a Common Lisp collection of assertions.
Confidence is a test framework for Common Lisp that focuses on simplicity. It avoids bureaucracy and makes it easy to work interactively, without a complicated setup, and with explicit functions and decisions.
KAPUTT is a test framework for Common Lisp that focuses on the following features:
KAPUTT is simple, it only defines three abstractions testcase, assertion and protocol and does not add any artefact on the backtrace when errors occur.
KAPUTT is extensible, it is possible to add problem-specific assertions to make test code more informative.
KAPUTT fits well interactive development.
lisp-unit is a Common Lisp library that supports unit testing. It is an extension of the library written by Chris Riesbeck.
Common Lisp port of the QuickCheck unit test framework
SHOULD-TEST is a methodology-agnostic and non-opinionated Common Lisp test framework, i.e. it doesn't care what kind of test approach you'd like to take.
The Lisp Critic scans your code for instances of bad Lisp programming practice.