A minimalist unit testing framework for Clojure and ClojureScript with a focus on simplicity and readability.
Expectations is a minimalist unit testing framework for Clojure and ClojureScript, designed to provide a simple and readable approach to writing tests. It focuses on reducing boilerplate and complexity, allowing developers to write clear assertions using a straightforward `expect` macro. The framework supports both Clojure and ClojureScript, enabling cross-platform testing workflows.
Clojure and ClojureScript developers who prefer a minimalist, non-`clojure.test` compatible testing framework for writing simple and readable unit tests.
Developers choose Expectations for its simplicity, clean syntax, and focus on readability, making it easier to write and maintain tests without the overhead of more complex testing frameworks. Its support for both Clojure and ClojureScript also provides flexibility for cross-platform projects.
A minimalist's unit testing framework ("classic" version)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses a simple `expect` macro for assertions, reducing boilerplate and improving test clarity, as emphasized in the README's focus on simplicity.
Runs tests in both Clojure and ClojureScript environments, enabling unified testing workflows for cross-platform projects, as noted in the key features.
Includes deliberately failing tests to verify error reporting and behavior, aiding in debugging and test validation, with 43 failing tests out of 128 total assertions as per the README.
Maintained as a stable 'classic' version in maintenance mode, suitable for projects that prioritize reliability over new features, as stated in the README.
Cannot be used with standard clojure.test tooling, limiting integration with common development and CI/CD workflows, as explicitly warned in the README.
As a legacy version, it receives minimal updates, which may not address emerging issues or support newer Clojure versions, reducing its long-term viability.
Running ClojureScript tests requires interactive REPL steps (e.g., via './scripts/repl'), as shown in the README, making it less streamlined compared to modern alternatives.