Missing graph on the coverage page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- php
- Domain
- data-visualization, testing
Research direction
Start by reviewing the coverage page changes in pull request 3348 and the current coverage-page implementation. Trace where coverage metrics are prepared and rendered, then restore a graph showing coverage evolution over time, including file and line coverage if both are available. Done means the graph appears on the coverage page with the expected historical metrics.
Written by the indexing model from the issue text.
Description
Bug report
Expected Behavior
Before 4.8 and the coverage page revamp from https://github.com/Kitware/CDash/pull/3348 we had a graph showing the coverage evolution over time. It is now missing.
Actual Behavior
Coverage over time graph is missing from the page.
CDash Version
v4.8.0
Additional Information
With the introduction of file coverage as well as line coverage, we could have two graphs, or two lines on the same graph, for the evolution of both metrics.
- Dominant language
- PHP
- Stars
- 248
- Forks
- 83
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 66
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Kitware/CDash
-
bug report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug report
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
bug report
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Kitware/CDash#3944 · 1 comment ·
Maintainers usually reply within 1 day
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
feature request
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
Talk Review
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
socallinuxexpo/scale-drupal#351 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
code4romania/cpc#47 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
mautic/api-library#351 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nunomaduro/collision#371 ·
-
Lead create/update: a product row without a "product_id" key passes LeadForm validation and fails in the database (500)Possibly taken @Arslan-TR claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
krayin/laravel-crm#2681 ·
Maintainers usually reply within 2 days