From a9b36b6b2dd96fa13326aed07bcc9f8ca2523721 Mon Sep 17 00:00:00 2001 From: Greg Graf Date: Sun, 29 Oct 2017 16:35:46 -0400 Subject: [PATCH] Correct examples in README.md In the sample code, `check-coverage` was being shown as a flag (with dashes) rather than a straight up command. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9dbce4fc1..fd7e1ec6d 100644 --- a/README.md +++ b/README.md @@ -154,14 +154,14 @@ nyc can fail tests if coverage falls below a threshold. After running your tests with nyc, simply run: ```shell -nyc --check-coverage --lines 95 --functions 95 --branches 95 +nyc check-coverage --lines 95 --functions 95 --branches 95 ``` nyc also accepts a `--check-coverage` shorthand, which can be used to both run tests and check that coverage falls within the threshold provided: ```shell -nyc --check-coverage --lines 100 npm test +nyc check-coverage --lines 100 npm test ``` The above check fails if coverage falls below 100%. @@ -169,7 +169,7 @@ The above check fails if coverage falls below 100%. To check thresholds on a per-file basis run: ```shell -nyc --check-coverage --lines 95 --per-file +nyc check-coverage --lines 95 --per-file ``` ## Running reports