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.
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.
Rove is a unit testing framework for Common Lisp applications. This is intended to be a successor of Prove.
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.
RT provides a framework for writing regression test suites.
This project was originally called cl-test-more. prove is yet another unit testing framework for Common Lisp. The advantages of prove are:
Various simple functions for testing and informative error messages
ASDF integration
Extensible test reporters
Colorizes the report if it's available (note for SLIME)
Reports test durations
NST is a unit/regression testing system for Common Lisp.
CLUnit2 is a Common Lisp unit testing framework. It is designed to be easy to use so that you can quickly start testing.
This package provides a simple Common Lisp library to print out the code coverage collected.
This is a small testing framework for Common Lisp. The entire API consists of: test, is, signals, finishes, run, suite and setf suite.
This package provides a simple Common Lisp library to print out the code coverage collected.
This project was originally called cl-test-more. prove is yet another unit testing framework for Common Lisp. The advantages of prove are:
Various simple functions for testing and informative error messages
ASDF integration
Extensible test reporters
Colorizes the report if it's available (note for SLIME)
Reports test durations
Common Lisp port of the QuickCheck unit test framework
This small library provides a way to replace the actual implementation of either regular or generic functions with mocks.
This is a randomized property-based testing library for Common Lisp. Rather than being a full-fledged general test framework in its own right, it's designed to embed randomized tests in whatever framework you like.
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.
This is a unit-testing framework for Common Lisp.
lisp-unit is a Common Lisp library that supports unit testing. It is an extension of the library written by Chris Riesbeck.
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.
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 package provides a Common Lisp test runner system SIMPLET.
NST is a unit/regression testing system for Common Lisp.
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.
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.
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.