All Projects → alfert → coverex

alfert / coverex

Licence: other
Coverage Reports for Elixir

Programming Languages

javascript
184084 projects - #8 most used programming language
elixir
2628 projects
CSS
56736 projects
HTML
75241 projects
shell
77523 projects

Projects that are alternatives of or similar to coverex

Bashcov
Code coverage tool for Bash
Stars: ✭ 113 (+15.31%)
Mutual labels:  coverage-report
cacao
Callable Cancer Loci - assessment of sequencing coverage for actionable and pathogenic loci in cancer
Stars: ✭ 21 (-78.57%)
Mutual labels:  coverage-report
enterprise
Code coverage done right.® On-premise enterprise version.
Stars: ✭ 63 (-35.71%)
Mutual labels:  coverage-report
Coverband
Ruby production code coverage collection and reporting (line of code usage)
Stars: ✭ 1,937 (+1876.53%)
Mutual labels:  coverage-report
javascript-test-reporter
DEPRECATED Code Climate test reporter client for JavaScript projects
Stars: ✭ 68 (-30.61%)
Mutual labels:  coverage-report
django-aws-eb-deploy
This is a GitHub action for automated deployment of Django projects to aws elastic beanstalk.
Stars: ✭ 24 (-75.51%)
Mutual labels:  coverage-report
Unittesting
Testing Sublime Text Packages
Stars: ✭ 95 (-3.06%)
Mutual labels:  coverage-report
behat-code-coverage
Generate Code Coverage reports for Behat tests
Stars: ✭ 48 (-51.02%)
Mutual labels:  coverage-report
covergates
The portal gates to coverage reports
Stars: ✭ 55 (-43.88%)
Mutual labels:  coverage-report
javadoc-coverage
A Doclet to generate JavaDoc coverage reports ☕️🧪📗
Stars: ✭ 23 (-76.53%)
Mutual labels:  coverage-report
Karma Coverage Istanbul Reporter
A karma reporter that uses the latest istanbul 1.x APIs to report coverage
Stars: ✭ 154 (+57.14%)
Mutual labels:  coverage-report
octocov
octocov is a toolkit for collecting code metrics (code coverage, code to test ratio and test execution time).
Stars: ✭ 191 (+94.9%)
Mutual labels:  coverage-report
continuous-integration-with-python
How to test your python code. How to automatically run your tests for your Python code. How to get reports of the tests coverage
Stars: ✭ 25 (-74.49%)
Mutual labels:  coverage-report
Typescript Coverage Report
Node command tool to generate TypeScript coverage report
Stars: ✭ 138 (+40.82%)
Mutual labels:  coverage-report
python-test-reporter
DEPRECATED Uploads Python test coverage data to Code Climate
Stars: ✭ 18 (-81.63%)
Mutual labels:  coverage-report
Codacy Coverage Reporter
Multi-language coverage reporter for Codacy
Stars: ✭ 96 (-2.04%)
Mutual labels:  coverage-report
jacoco-badge-generator
Coverage badges, and pull request coverage checks, from JaCoCo reports in GitHub Actions
Stars: ✭ 53 (-45.92%)
Mutual labels:  coverage-report
goverreport
Command line tool for coverage reporting and validation
Stars: ✭ 44 (-55.1%)
Mutual labels:  coverage-report
unitest
🌎 Seamless node and browser unit testing with code coverage
Stars: ✭ 28 (-71.43%)
Mutual labels:  coverage-report
react-testing-mocha-chai-enzyme
A solid test setup for React components with Mocha, Chai, Sinon, Enzyme in a Webpack/Babel application.
Stars: ✭ 48 (-51.02%)
Mutual labels:  coverage-report

Coverex

Coverex is an Elixir Coverage tool used by mix. It provides tables with overviews of module and function coverage data, includings links to annotated source code files.

Build Status Coverage Status hex.pm version

Configuration

Coverex is completely configured via mix.exs of your project. To enable Coverex, you add this line to your mix.exs file

test_coverage: [tool: Coverex.Task]

as part of the regular project settings. In addition to that, you need to add Coverex to the dependencies of your project. Coverex is available via hex.pm, so you need only to add this line to the dependencies in your mix.exs file:

{:coverex, "~> 1.4.10", only: :test}

For debugging purposes, the log level can be set as addition to the tool option. The default value is :error. To set the log level to :debug you use this line in your mix.exs file:

test_coverage: [tool: Coverex.Task, log: :debug]

The usual log levels of the Logger application of Elixir are available.

If you set the flag coveralls: true and you are running on travis-ci, the coverage information are sent to http://coveralls.io . An example configuration would be

test_coverage: [tool: Coverex.Task, coveralls: true]

Since coverex 1.4.7, a summary on the module level is printed on the console. You can switch this off by setting the option console_log to false.

test_coverage: [tool: Coverex.Task, console_log: false]

If you want to ignore some of the modules to appear in the coverage reports, e.g because they are generated automatically and therefore often needs no test coverage, you can do this since coverex 1.4.8. Use the option ignore_modules and assign to it a list of module names to ignore.

test_coverage: [tool: Coverex.Task, ignore_modules: [Database, Database.User]]

Since coverex 1.4.10 the from the Elixir compiler automatically generated functions __info__ and __struct__ are removed from the list of covered functions. It simply makes no sense to include them into the list (see also #24).

Running Coverex

If you have configured Coverex as described above you can run Coverex as a drop-in replacement for the regular coverage mechanism of mix:

$> mix test --cover

The coverage reports are found in the cover directory or what you have configured as coverage directory as explained in the docs of the Mix.Tasks.Test task.

Contributing

Please use the GitHub issue tracker for

  • bug reports and for
  • submitting pull requests

License

Coverex is provided under the Apache 2.0 License.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].