explain why urchin is called urchin

This commit is contained in:
Thomas Levine 2016-01-29 17:28:26 +00:00
parent 2be0151213
commit 96ab43c233
2 changed files with 5 additions and 0 deletions

View File

@ -13,6 +13,7 @@ Version 0.0.6
* Pass the -e flag to exit urchin if any single test fails. * Pass the -e flag to exit urchin if any single test fails.
* Remove the undocumented, experimental -x flag now that shall exists. * Remove the undocumented, experimental -x flag now that shall exists.
* Display version number with the -v flag. * Display version number with the -v flag.
* Document why Urchin is called "Urchin"
These changes are made somewhat separately in the branches "exit-on-fail", These changes are made somewhat separately in the branches "exit-on-fail",
"remove-urchin-x", "tap", and "update-readme". They are rebased into one "remove-urchin-x", "tap", and "update-readme". They are rebased into one

View File

@ -8,6 +8,10 @@ Urchin is a file-based test harness, normally used for testing shell programs.
It is written in portable shell and should thus work on GNU/Linux, BSD It is written in portable shell and should thus work on GNU/Linux, BSD
(including Mac OS X), and other Unix-like platforms. (including Mac OS X), and other Unix-like platforms.
Urchin is called "Urchin" because
[sea urchins](https://en.wikipedia.org/wiki/Sea_urchin)
have shells called "tests".
## Try it out ## Try it out
Urchin's tests are written in Urchin, so you can run them to see what Urchin Urchin's tests are written in Urchin, so you can run them to see what Urchin
is like. Clone the repository is like. Clone the repository