-
Notifications
You must be signed in to change notification settings - Fork 29
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
Move trends plots inside of "Custom" section #3404
Conversation
@@ -3,25 +3,31 @@ import omit from 'lodash.omit' | |||
import isEmpty from 'lodash.isempty' |
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.
The test coverage on the diff in this pull request is 91.2% (85% is the threshold).
I looked over the code and everything looked pretty covered. Any thing I could have missed to improve the coverage?
renderAppWithOptionalData({ | ||
checkpoint: checkpointPlotsFixture | ||
comparison: comparisonTableFixture, | ||
custom: customPlotsFixture |
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.
custom
won't render currently without additional data. Planning to changing that and will adjust tests according.
I believe #3404 (comment) has been resolved with #3466 and #3491 (both approved and ready to be merged into this pr)! Here's a (hopefully complete) list of what's left:
Anything else that should get taken care of before we merge this? Or did I miss anything when I took care of merge conflicts? |
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.
I think you used to have something that blocked the following from happening before:
Screen.Recording.2023-03-20.at.8.46.26.AM.mov
Could be easy to just show the available choice from the list. (Can be a follow-up)
Thanks for spotting that! Simple bug in the quick pick logic/tests that I missed earlier. Will fix it before merging since I'd prefer to stop users' custom plot state having copies of the same plot in it :) Will keep current logic for now and save choosing available choices for a followup. |
Code climate seems to be failing with
First guess is the issue is amount of lines being covered:
Will see if upping the code coverage fixes the issue! |
Updated the tests based of code reviews and looking over things myself:
But code coverage is still failing just shy of
Last things I'm seeing regarding testing is:
I'll start working on the followup on stopping a user from recreating custom plots since I think it will take about the same time as just creating tests for our current solution. But is there something else that could be going on with CodeClimate that I'm missing? cc @sroy3, @mattseddon |
We've merged too many things with low code coverage. We've pretty much hit the limit where we either get 100% coverage on a PR or else coverage will fail. I'll try to add coverage where it's missing if possible. Other than that, we have 2 other options from now on. Always hitting 100% coverage until the situation gets better or lower threshold to something lower (90%?). |
Code Climate has analyzed commit 2945e34 and detected 5 issues on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 96.4% (85% is the threshold). This pull request will bring the total coverage in the repository to 95.0%. View more on Code Climate. |
1/3 main <= this <= #3466 <= #3491
Demo
Screen.Recording.2023-03-11.at.6.03.48.PM.mov
Part of #3373