Skip to content

Commit 2f63a63

Browse files
committed
Prep for 1.1.0 release
1 parent 6a91708 commit 2f63a63

File tree

3 files changed

+5
-3
lines changed

3 files changed

+5
-3
lines changed

CHANGELOG.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
1-
# Version 1.1.0 in progress
1+
# Version 1.1.0 -- 2019-01-08
22

33
* An expectation can now use a qualified keyword spec to test conformance of the actual value. Failures are reported with the spec explanation. #2
44
* If Paul Stadig's Humane Test Output is available (on the classpath), failure reporting is automatically made compatible with it. Expectations that use data structure "equality" (the `=?` extension to `is`) will produce "humane" output for failures, showing differences. #1
55

6-
# Initial version 1.0.1
6+
# Initial version 1.0.1 -- 2019-01-02

README.md

+2
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,7 @@ Here we see the predicate (`odd?`) being applied in the "actual" result from
111111
`expectations.clojure.test` supports the following features from Expectations so far:
112112
* simple equality test
113113
* simple predicate test
114+
* spec test (using a keyword that identifies a spec)
114115
* class test -- see `named` above
115116
* exception test -- see `divide-by-zero` above
116117
* regex test -- see `regex-1` and `regex-2` above
@@ -167,6 +168,7 @@ to be aware of:
167168

168169
* 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.
169170
* Because of that, tests run when you decide, not at JVM shutdown (which is the default with Expectations).
171+
* If you have [Paul Stadig's Humane Test Output](https://github.com/pjstadig/humane-test-output) on your classpath, it will be activated and failures reported by `=?` will be compatible with it, providing better reporting.
170172
* Instead of the `in-context`, `before-run`, `after-run` machinery of Expectations, you can just use `clojure.test`'s fixtures machinery (`use-fixtures`).
171173
* 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").
172174
* `freeze-time` and `redef-state` are not (yet) implemented.

pom.xml

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<modelVersion>4.0.0</modelVersion>
44
<groupId>expectations</groupId>
55
<artifactId>clojure-test</artifactId>
6-
<version>1.0.1</version>
6+
<version>1.1.0</version>
77
<name>exp-clojure-test</name>
88

99
<description>A clojure.test-compatible version of the classic Expectations testing library.</description>

0 commit comments

Comments
 (0)