Skip to content

Commit 8c6e243

Browse files
committed
docs(readme): disambiguate rationale sentence
1 parent 730157a commit 8c6e243

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Features:
1313
- access cumulative failure, pass, and skip counts as shell variables
1414
- print coverage summaries with test count, failure count and rate, pass count and rate, and skip count
1515

16-
What it does not feature: its own human language-like declarative test syntax. There's no "describe", "expect", etc. Downside is the tests don't read like a story. Upside is —because the shell already has rich support for tests— there is nothing to learn, there are no artificial limits on what can be tested, the cost to migrating to zsh-test-runner (or from, if you must) is very low, and tests are completely reliable with no question of whether they were correctly implemented. Just write your `[[ ]]`s, your `(( ))`s, even your `test`s or `[ ]`s, and never again punt on testing.
16+
What it does not feature: its own human language-like declarative test syntax. There's no "describe", "expect", etc. Downside is the tests don't read like a story. Upside is —because the shell already has rich support for tests— there is nothing to learn, there are no artificial limits on what can be tested, the cost to migrating to zsh-test-runner (or from, if you must) is very low, and there is no risk that assertions were incorrectly implemented. Just write your `[[ ]]`s, your `(( ))`s, even your `test`s or `[ ]`s, and never again punt on testing.
1717

1818
## Installation
1919

0 commit comments

Comments
 (0)