From 968b5098f31862c2efd4cc0b7693d5e2e875146b Mon Sep 17 00:00:00 2001 From: Kyle Welch Date: Fri, 30 Sep 2016 00:39:28 -0500 Subject: [PATCH] updated docs on coverage command --- docs/FAQ.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index 8b5ecefa9..c0b69029b 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -216,11 +216,10 @@ Install the [Redux devtools extension](https://chrome.google.com/webstore/detail Hot reloading doesn't always play nicely with stateless functional components at this time. [This is a known limitation that is currently being worked](https://github.com/gaearon/babel-plugin-react-transform/issues/57). To avoid issues with hot reloading for now, use a traditional class-based React component at the top of your component hierarchy. ### How do I setup code coverage reporting? -Using the `npm run test:cover` command to run the tests, building a code coverage report. The report is written to `coverage/index.html`. A quick way to check coverage is: +Using the `npm run test:cover` command to run the tests, building a code coverage report. The report is written to `coverage/index.html`. Slingshot simplifies provides a script for this: ```bash -npm run test:cover -open ./coverage/index.html +npm run open:cover ``` You can add code coverage metrics to your `README.md` file and pull by integrating with [Coveralls](https://coveralls.io/).