You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -15,11 +15,11 @@ after_success:
15
15
```
16
16
17
17
### Produce Coverage Reports
18
-
[`coverage.py`](https://bitbucket.org/ned/coveragepy) is required to collect coverage metrics.
18
+
[coverage.py](https://github.com/nedbat/coveragepy) is required to collect coverage metrics.
19
19
20
20
Below are some examples on how to include coverage tracking during your tests. Codecov will call `coveragexml -i` automatically to generate the coverage xml output, which will be archived and processed server side.
21
21
22
-
You may need to configure a `.coveragerc` file. Learn more [here](http://coverage.readthedocs.org/en/latest/config.html>). Start with this [generic .coveragerc](https://gist.github.com/codecov-io/bf15bde2c7db1a011b6e>) for example.
22
+
You may need to configure a `.coveragerc` file. Learn more [here](http://coverage.readthedocs.org/en/latest/config.html). Start with this [generic .coveragerc](https://gist.github.com/codecov-io/bf15bde2c7db1a011b6e) for example.
23
23
24
24
We highly suggest adding `source` to your `.coveragerc` which solves a number of issues collecting coverage.
25
25
@@ -40,7 +40,7 @@ pytest --cov=./
40
40
```
41
41
nosetest --with-coverage
42
42
```
43
-
See the [Offical Nose coverage docs](http://nose.readthedocs.org/en/latest/plugins/cover.html>) for more information.
43
+
See the [Offical Nose coverage docs](http://nose.readthedocs.org/en/latest/plugins/cover.html) for more information.
44
44
45
45
### Testing with ``tox``
46
46
@@ -54,12 +54,12 @@ commands = codecov
54
54
55
55
### FAQ
56
56
- Q: What's the difference between the codecov-bash and codecov-python uploader?
57
-
A: As far as python is concerned, *nothing*. You may choose to use either uploader. Codecov recommends **using the bash uploader when possible** as it supports more unique repository setups. Learn more at [codecov/codecov-bash](https://github.com/codecov/codecov-bash>) and [codecov/codecov-python](https://github.com/codecov/codecov-python>).
57
+
A: As far as python is concerned, *nothing*. You may choose to use either uploader. Codecov recommends **using the bash uploader when possible** as it supports more unique repository setups. Learn more at [codecov/codecov-bash](https://github.com/codecov/codecov-bash) and [codecov/codecov-python](https://github.com/codecov/codecov-python).
58
58
- Q: Why am I seeing `No data to report`?
59
59
A: This output is written by running the command `coverage xml` and states that there were no `.coverage` files found.
60
60
1. Make sure coverage is enabled. See Enabling Coverage
61
61
2. You may need to run `coverage combine` before running Codecov.
62
-
3. Using Docker? Please follow this step: [Testing with Docker: Codecov Inside Docker](https://github.com/codecov/support/wiki/Testing-with-Docker#codecov-inside-docker>).
62
+
3. Using Docker? Please follow this step: [Testing with Docker: Codecov Inside Docker](https://github.com/codecov/support/wiki/Testing-with-Docker#codecov-inside-docker).
63
63
- Q: Can I upload my `.coverage` files?
64
64
A: **No**, these files contain coverage data but are not properly mapped back to the source code. We rely on `coveragepy` to handle this by calling `coverage xml` in the uploader.
0 commit comments