NOTE: Clojars has introduced a Verified Group Names policy which means no new libraries can be pushed to the
expectationsgroup, anddoofilters out JAR artifacts that beginclojure-for self-hosted ClojureScript environments (i.e.,planck), continuing to useclojure-testfor the artifact name is not viable. Accordingly, the 2.x versions of this library are published ascom.github.seancorfield/expectations.
(defexpect foo) and (defexpect foo (bar)) match the behavior of deftest, without wrapping the body in (expect ,,,). This is potentially breaking insofar as (defexpect foo (produces-falsey)) would have been a failing test in 1.x but now silently just runs (produces-falsey) in the same way that (deftest foo (produces-falsey)) does.clojure.test, for convenience in dev/test so users don't need to require clojure.test as well.cljs.test's version of use-fixtures: accepts functions or hash maps (containing :before and/or :after keys with 0-arity functions).in, from-each, more-of, more->, more are really only syntactic constructs inside expect).planck -- see https://github.com/clojure-expectations/clojure-test/pull/16 for details (@kkinear).in; allow it to be combined with more etc. #11side-effects.expect. #9more-> equivalent to thrown-with-msg?. #5between and between' for inclusive and exclusive range checking.in with a hash map to correctly detect failing cases.:require .. :refer in README to list all public symbols. #4^:no-doc metadata for cljdoc.org.=? extension to is) will produce "humane" output for failures, showing differences. #1(broken version)
Can you improve this documentation?Edit on GitHub
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |