-
Notifications
You must be signed in to change notification settings - Fork 45
Update cov tab image #2598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update cov tab image #2598
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -39,6 +39,29 @@ | |||||
| end="<!--tabs-end-->" | ||||||
| %} | ||||||
|
|
||||||
| ## Coverage tab | ||||||
|
|
||||||
| The Coverage tab provides a detailed breakdown of how your changes impact the project's test coverage. It allows you to ensure that new code is properly tested before it is merged. | ||||||
|
Check failure on line 44 in docs/repositories/pull-requests.md
|
||||||
|
|
||||||
| **Coverage Overview** | ||||||
| At the top of the tab, two primary indicators give you an immediate health check of the Pull Request: | ||||||
|
|
||||||
| * **Diff Coverage**: The percentage of new or modified executable lines that are covered by tests. | ||||||
| * **Coverage Variation**: The net impact (increase or decrease) the PR has on the overall project coverage percentage. | ||||||
|
|
||||||
| **File Breakdown** | ||||||
| On the left sidebar, you can find a list of all files modified in the PR. For each file, Codacy displays its specific diff coverage percentage, helping you quickly identify which parts of your contribution might be missing tests. | ||||||
|
Check warning on line 53 in docs/repositories/pull-requests.md
|
||||||
|
|
||||||
| **Diff Visualization** | ||||||
| The main view displays the code changes with a specialized coverage overlay to pinpoint exactly what is being tested: | ||||||
|
Check failure on line 56 in docs/repositories/pull-requests.md
|
||||||
|
|
||||||
| * **Covered Lines (Green)**: Lines executed by your test suite. These are marked with a green highlight and a label indicating the number of hits (e.g., 1 hits), representing how many times that line was executed during the test run. | ||||||
|
Check failure on line 58 in docs/repositories/pull-requests.md
|
||||||
|
Comment on lines
+47
to
+58
|
||||||
| * **Uncovered Lines (Red)**: Executable lines that were not reached by any tests. These are marked with a red highlight and a Not covered label. | ||||||
|
Check failure on line 59 in docs/repositories/pull-requests.md
|
||||||
|
|
||||||
|
Comment on lines
+55
to
+60
|
||||||
| *Note: Lines that are not executable (like comments or empty lines) will not show a coverage status.* | ||||||
|
Check failure on line 61 in docs/repositories/pull-requests.md
|
||||||
|
|
||||||
|  | ||||||
|
||||||
|  | |
|  |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
List items in this new section use
*and a single space, but the repo's markdownlint config enforces dash-style lists and spacing (MD004 style "dash" and MD030/MD007). Please switch these bullets to-with the expected spacing so linting passes consistently.