Open sktoiva opened 9 years ago
it looks as if the return value from calling the test function is making its way into cider as some kind of emacs data structure, and that cider is expecting a string for some reason.
alternatively, instead of being related to the test return value it might be related to something passed to the clojure.test
reporting functions. @lackita any guesses?
@sktoiva I'm also curious what happens if you used defspec
instead.
defspec
works as intended, or at least so that the *cider-test-report*
buffer contains information about failed tests and the specific information about how it failed is printed to *cider-repl*
.
I'm using Emacs
25.0.50.1
and CIDER0.10.0snapshot
.Given the following example:
Running test with
cider-test-run-test
orcider-test-run-tests
, the reporting will fail with following error message:I have tested it without the
checking
macro:This works as intended, so currently I'm assuming the error has something to do with test.chuck and not CIDER itself.
However, invoking the tests with
(clojure.test/run-tests)
provides the intended output, so I'm a bit loss here where the problem might lie.