You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+13
Original file line number
Diff line number
Diff line change
@@ -338,6 +338,19 @@ To setup protractor e2e tests, you must first run
338
338
339
339
Use `grunt test:e2e` to have protractor go through tests located in the `e2e` folder.
340
340
341
+
**Code Coverage**
342
+
343
+
Use `grunt test:coverage` to run mocha-istanbul and generate code coverage reports.
344
+
345
+
`coverage/server` will be populated with `e2e` and `unit` folders containing the `lcov` reports.
346
+
347
+
The coverage taget has 3 available options:
348
+
-`test:coverage:unit` generate server unit test coverage
349
+
-`test:coverage:e2e` generate server e2e test coverage
350
+
-`test:coverage:check` combine the coverage reports and check against predefined thresholds
351
+
352
+
**when no option is given `test:coverage` runs all options in the above order*
353
+
341
354
## Environment Variables
342
355
343
356
Keeping your app secrets and other sensitive information in source control isn't a good idea. To have grunt launch your app with specific environment variables, add them to the git ignored environment config file: `server/config/local.env.js`.
0 commit comments