Skip to content

Commit 7563519

Browse files
committed
Note that CustomPred is not implemented
It isn't documented in Expectations (and I expect it is very rarely used).
1 parent 465e1fd commit 7563519

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,10 +156,11 @@ compatibility with `clojure.test`-based tooling -- here are the other difference
156156
to be aware of:
157157

158158
* You use standard `clojure.test`-based tooling -- `lein test`, `boot test`, and [Cognitect's `test-runner`](https://github.com/cognitect-labs/test-runner) -- instead of the Expectations-specific tooling.
159-
* Because of that, tests run when you decide, not at the end of the JVM (as happens with Expectations).
159+
* Because of that, tests run when you decide, not at JVM shutdown (which is the default with Expectations).
160160
* Instead of the `in-context`, `before-run`, `after-run` machinery of Expectations, you can just use `clojure.test`'s fixtures machinery (`use-fixtures`).
161161
* Instead of Expectations' concept of "focused" test, you can use metadata on tests and tell your test runner to "select" tests as needed (e.g., Leiningen's "test selectors", Boot's "filters").
162162
* `freeze-time` and `redef-state` are not (yet) implemented.
163+
* The undocumented `CustomPred` protocol is not implemented -- you can use plain `is` and extend `clojure.test`'s `assert-expr` multimethod if you need that level of control.
163164

164165
## Test & Development
165166

0 commit comments

Comments
 (0)