Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Added ability to get code coverage (for use with an online tool) #6473

Closed
jkup opened this issue Dec 30, 2016 · 0 comments
Closed

Added ability to get code coverage (for use with an online tool) #6473

jkup opened this issue Dec 30, 2016 · 0 comments
Assignees
@bsclifton
Labels
automated-tests QA/checked QA/test-plan-specified release-notes/exclude
Milestone
0.14.0

Comments

@jkup
Copy link
Contributor

jkup commented Dec 30, 2016 •
edited by bsclifton
Loading

Test plan

  1. git clone git@github.com:brave/browser-laptop.git
  2. cd browser-laptop
  3. npm run unittest-cov
  4. you should see a very nice color coded dump of all files and their coverage

Original issue description

Now that we have some great test tools integrated it might be cool to add a code coverage tool. As far as I know they all integrate with Travis CI and are all free for open source projects! The big ones I think are:

https://coveralls.io/
https://codecov.io/
https://codeclimate.com/

It would be cool if these were easy to integrate and could help us move towards better test coverage!
@jkup jkup self-assigned this Dec 30, 2016
@jkup jkup added automated-tests needs-investigation A bug not 100% confirmed/fixed that needs QA to better audit. labels Dec 30, 2016
bsclifton added a commit that referenced this issue Feb 26, 2017
@bsclifton
Added new unittest-cov npm task which reports (via CLI) code covera…
42e1854 
…ge using istanbul.

Auditors: @alexwykoff, @bbondy

Fixes #6473
@bsclifton bsclifton mentioned this issue Feb 26, 2017
Merged
4 tasks
@bsclifton bsclifton self-assigned this Feb 26, 2017
@bsclifton bsclifton modified the milestones: 0.13.5, 0.13.6 Feb 26, 2017
@bsclifton bsclifton changed the title Investigate code coverage tool Be able to get code coverage Mar 2, 2017
@bsclifton bsclifton changed the title Be able to get code coverage Be able to get code coverage (for use with an online tool) Mar 2, 2017
@bsclifton bsclifton added QA/test-plan-specified release-notes/include and removed needs-investigation A bug not 100% confirmed/fixed that needs QA to better audit. labels Mar 2, 2017
This was referenced Mar 14, 2017
Closed
Closed
Closed
Closed
Closed
This was referenced Mar 17, 2017
Closed
Closed
Closed
Closed
Closed
Closed
This was referenced Mar 21, 2017
Closed
Closed
@alexwykoff alexwykoff changed the title Be able to get code coverage (for use with an online tool) Added ability to get code coverage (for use with an online tool) Mar 28, 2017
This was referenced Mar 28, 2017
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bsclifton bsclifton

Labels
automated-tests QA/checked QA/test-plan-specified release-notes/exclude
Projects
None yet
Milestone
0.14.0
Development

No branches or pull requests
3 participants
@jkup @luixxiul @bsclifton