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
|`-t`|`CODECOV_TOKEN`| Private repo token for uploading |
21
+
|`-e`|`CODECOV_ENV`| List of config vars to store for the build |
22
+
|`-F`|| Flag this upload to group coverage reports. Ex. `unittests` or `integration`|
23
+
16
24
# How to generate coverage reports
17
25
18
26
[coverage.py](https://bitbucket.org/ned/coveragepy) is required to collect coverage metrics. Below are some examples on how to include coverage tracking during your tests. Codecov will call `coverage xml -i` automatically to generate the coverage xml output, which will be archived and processed server side.
@@ -75,7 +83,9 @@ This output is written by running the command `coverage xml` and states that the
75
83
76
84
**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.
77
85
86
+
####? How can I integrate with CICD providers?
78
87
88
+
Please see the documentation at our [Python repository](https://github.com/codecov/codecov-python/blob/master/README.md#ci-providers)
0 commit comments