Coveralls-merge
Get coverage data on Python C extensions, on both the python side and the C side of the api. The package combines the output from coverage-lcov and coveralls to upload your coverage data to coveralls.io.
This only supports travis-ci.
Usage
Setup coveralls, and make sure that it’s working with coveralls.io for the python portion. Then, to add c coverage, add a few lines to your .travis.yml:
python:
- 2.7
install:
# install lcov
- "sudo apt-get -qq install lcov"
# install test runners, coveralls, and coveralls-merge
- "pip install coveralls nose coveralls-merge"
# install the lcov parser
- "gem install coveralls-lcov"
script:
- coverage erase
- python setup.py clean
# build, using coverage flag
- CFLAGS="-coverage" python setup.py build_ext --inplace
# run your tests, with coverage as normal
- coverage run -m nose Tests/test_*.py
after_success:
# combine and generate json
- lcov --capture --directory . -b . --output-file coverage.info
- coveralls-lcov -v -n coverage.info > coverage.c.json
# upload
- coveralls-merge coverage.c.json
Changelog
0.0.3 (2018-01-25)
Strip parameter to strip leading directories in site-packages from path
0.0.2 (2014-07-30)
Requests fix
Doc Changes
0.0.1 (2014-07-30)
Initial upload
1 maintainer
Metadata
1 maintainer
Release files for coveralls-merge 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| coveralls-merge-0.0.3.tar.gz | 4.8 kB | Without provenance | Details for coveralls-merge-0.0.3.tar.gz |
Release files / coveralls-merge-0.0.3.tar.gz
| Download URL | coveralls-merge-0.0.3.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e7662e9960bb375528e35c4aa54e96467c2cfb8de32e5918ee2ce0de84be06f
|
|
BLAKE2b-256 checksum How to use checksums |
1f4aaf2413b78ba9361a3e18a58788e745c89772325b100d62a3bc217c295f15
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for coveralls-merge 0.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
