-
Right now it appears (at least with Travis) that coveralls always does comparisons against master when deciding how much coverage increases/decreases. This is problematic on an active project where t…
-
- [x] travis
- [ ] npm run test
-
I think as a standard, it would b nice to add visible test coverage to the project. This can be achieved through https://coveralls.io/
-
I'm thinking the first item will be coveralls. That will be easy I think to make a universal size and unisex. It will also make it very easily recognizable as you don't see a lot of coveralls in the c…
-
It would be cool to use something like [coveralls]( https://coveralls.io/ ) or [codecov]( https://codecov.io/ ) to provide a way to visualize the testsuite's coverage.
-
Always handy to see stuff like that, leaning towards [Coveralls.io](https://coveralls.io/) at the moment.
We can use [Poncho](https://github.com/deepsweet/poncho) and it doesn't look too difficult.
-
All the samples use the same package space. This is generally not a good idea. In order to fix coveralls so it works during github actions, all the samples need to be put into their own name spaces.…
-
- Add unit tests and bdd tests to improve coverage
- Place all configs of coverage.py into .coveragerc
- Set up coveralls in CI
-
We should utilize coveralls.io to analyze and track our test coverage.
-
Hi,
when running
`istanbul cover ./node_modules/mocha/bin/_mocha --report lcovonly -- -R spec && cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js && rm -rf ./coverage`
I'm getting…