From c2cfdfcd0d6881492ce7f61f03b3451c42bff7be Mon Sep 17 00:00:00 2001 From: Leah Wasser Date: Wed, 1 Nov 2023 13:41:58 -0600 Subject: [PATCH] Update ci-tests-data/code-cov.md Co-authored-by: Nick Murphy --- ci-tests-data/code-cov.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ci-tests-data/code-cov.md b/ci-tests-data/code-cov.md index a8624a98..048e8d1f 100644 --- a/ci-tests-data/code-cov.md +++ b/ci-tests-data/code-cov.md @@ -8,6 +8,6 @@ A common service for analyzing code coverage is [codecov.io](https://codecov.io/ :height: 450px :alt: Screenshot of the code cov service - showing test coverage for the stravalib package. in this image you can see a list of package modules and the associated number of lines and % lines covered by tests. at the top of the image you can see what branch is being evaluated and the path to the repository being shown. -the Code cov platform is a useful tool if you wish to visually track code coverage. Using it you can not only get the same summary information that you can get with **pytest-cov** extension. You can also get a visual representation of what lines are covered by your tests and what lines are not covered. Code cove is mostly useful for evaluating unit tests and/or how much of your package code is "covered. It however will not evaluate things like integration tests and end-to-end workflows. b +the Code cov platform is a useful tool if you wish to visually track code coverage. Using it you can not only get the same summary information that you can get with **pytest-cov** extension. You can also get a visual representation of what lines are covered by your tests and what lines are not covered. Code cove is mostly useful for evaluating unit tests and/or how much of your package code is "covered. It however will not evaluate things like integration tests and end-to-end workflows. ```