Skip to content

Fix links in README.md #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 6, 2019
Merged

Fix links in README.md #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,9 +137,9 @@ would want to migrate your Expectations test suite to `clojure.test`-style
named tests? The short answer is **tooling**! Whilst Expectations has
well-maintained, stable plugins for Leiningen and Boot, as well as an Emacs mode,
the reality is that Clojure tooling is constantly evolving and most of those
tools -- such as the excellent [https://cider.readthedocs.io/en/latest/](CIDER),
[https://cursive-ide.com/](Cursive),
and the more recent [https://atom.io/packages/proto-repl](ProtoREPL)
tools -- such as the excellent [CIDER](https://cider.readthedocs.io/en/latest/),
[Cursive](https://cursive-ide.com/),
and the more recent [ProtoREPL](https://atom.io/packages/proto-repl)
and [Chlorine](https://atom.io/packages/chlorine) (both for Atom) --
are going to focus on Clojure's built-in testing library first.
Support for the original form of Expectations, using unnamed tests, is
Expand All @@ -156,8 +156,8 @@ hashcode of the text form of the `expect` body), which means the test
name changes whenever the text of the test changes. To address that, the new
`expectations.clojure.test` namespace introduces named expectations via
the `defexpect` macro (mimicking `clojure.test`'s `deftest`
macro). Whilst this goes against the [https://clojure-expectations.github.io/odds-ends.html](Test Names
philosophy) that Expectations was created with, it buys us a lot in terms of
macro). Whilst this goes against the [Test Names
philosophy](https://clojure-expectations.github.io/odds-ends.html) that Expectations was created with, it buys us a lot in terms of
tooling support!

## Differences from Expectations
Expand Down