-
Currently, only integration tests are reported to coveralls.io. Ideally, we'd have these tests separated out so they could both be reported separately.
-
Here is my directory structure:
![screenshot 2016-04-11 14 31 22](https://cloud.githubusercontent.com/assets/11139560/14443201/8f9524fa-fff2-11e5-924e-ce8bf9f9ba4e.png)
When I run:
`istanbul report…
-
Currently certain PR's coming from forks result in the action running in the context of the fork, which means it can't post a comment or a PR review to the PR/issue.
#### Possible workarounds:
1…
-
Since we have both a `mix test` and `mix coveralls` our tests end up running twice, we could save half the time by figuring out how to consolidate it.
-
Let's hit this milestone of bringing test coverage over 85%.
Once that happens, we'll pin the Coveralls validation to ensure that it does not drop below this.
-
There are modules (such as https://pypi.python.org/pypi/coverage), which allows to measure the code coverage. If run on unit test, one can measure the amount of code covered by the tests.
I propose…
-
See report here: https://github.com/Hoverbear/rust-rosetta/pull/563
-
## Hi Team as part security and vulnerability checking we have downloaded code and did npm audit:
we found 27 vulnerabilities which are high and critical and moderate in number. please find bellow lo…
-
It will be nice to have test coverage and unit tests passing shield, but I should try and pick tools for that.
[Coveralls](https://coveralls.io/) seems great.
-
* sonarcloud https://docs.travis-ci.com/user/sonarcloud/
* https://coveralls.io
* https://docs.travis-ci.com/user/customizing-the-build/#build-matrix / https://docs.travis-ci.com/user/languages/php/