Using test.check with expectations is simple, but the standard failure message leaves a bit to be desired in my opinon. However, you can use an expectations.CustomPred and get much better failure reports when things go poorly.
;;; results from using expectations and simple-check without a CustomPred
failure in (core_test.clj:18) : simple-expectations.core-test
(expect {:resulttrue} (in (sc/quick-check100 prop-no-42)))
expected: {:resulttrue}
in: {:resultfalse, :failing-size42, :num-tests43, :fail [[7-16033-3742-36]], :shrunk {:total-nodes-visited14, :depth6, :resultfalse, :smallest [[42]]}}
:result expected: true
was: false;;; results from using expectations and simple-check with a CustomPred
failure in (core_test.clj:31) : simple-expectations.core-test
(expect (->SimpleCheck) (sc/quick-check100 prop-no-42))
52 of 53 failures
fail: [[-8-29-37-37-1536-22952-6-151516-65-17-10-48162920-214245-45-4237363128-33-24-71]]
shrunk: [[42]]
Ran 2 tests containing 2 assertions in 84 msecs
2 failures, 0 errors.Copyright © 2014 FIXME
Distributed under the Eclipse Public License either version 1.0 or (at your option) any later version.