Test Result Trend Graphs changed to bar charts
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- php
- Domain
- data-visualization, frontend
Research direction
Start by reproducing the Test Result Trend Graphs in CDash 5.3.0 and trace the chart-rendering entry point used by the trend results view. Compare the current bar-chart behavior with the reported former line charts and verify that the y-axis is scaled around the actual data; done means small run-to-run changes are visibly distinguishable in Chrome and Firefox.
Written by the indexing model from the issue text.
Description
Bug report
Expected Behavior
My developers/PM brought this to me and I did not even know that CDash did/could do this, my apologies if I get some terms wrong.
In a software project we are reporting test results back to CDash, CDash is graphing trends in the test results. We like that. Apparently the graphs changed from lines to the bar charts, with the scale always being zero to some max. They used to be lines with the y-axis scale zoomed around the actual data.
The current trend charts make it difficult to see small changes from run to run.
Is it possible to get the old behavior back, with the y-axis zoomed around the actual data?
CDash Version
5.3.0
Additional Information
Add additional information here if necessary. Helpful information includes:
Browser is current Chrome or Firefox on Windows
Thanks,
Chad
- 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
-
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
-
feature request
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
[Sync EN] Fix session read handler docs: false reports a failure, not a missing session (#5902)Opensync-en
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[Sync EN] Fix session read handler docs: false reports a failure, not a missing session (#5902)Opensync-en
Difficulty 2/5 1-2 days Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
feature-request needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aws/aws-sdk-php#3365 ·
Maintainers usually reply within 1 day