We'd love your feedback!

[kylemann]

Thanks for dropping by! 👋

We've been iterating and updating the web app experience and would love your feedback about:

• What do you think about the new UI changes?
• What would you'd like to see improved?
• What are challenges you've experienced?
• How do you use the tool today? What parts do you use?
• If you don't use the web tool: why not?
• How could we better help your workflow?
• Any general thoughts you'd like to share!

We greatly appreciate your time and thoughts - looking forward to hearing from you ❤

Codecov team

This issue is intended to share and collect feedback about the tool. If you have support needs or questions, please see our support page.

Oha

[nikiizvorski]

I have a massive problem on the UI actually. I have a branch that shows my coverage without any problems and when i go to main screen where it's the same branch that i setup as default says there are no files to compare and doesn't show my files but shows coverage just files aren't accessible from there.

Otherwise i love Codecov. It's just great! And the new design is great!

[jonaldinger]

@kylemann great to see UI improvements landing. Since you asked, here's some feedback based the things you mentioned you were looking for...

What do you think about the new UI changes?

I just saw the new logged-in landing page for the first time. Definitely a nice improvement! I like the table of repos/date updated/coverage %. Makes it really easy to digest the information at-a-glance, and it's then easy to navigate into each repo 👏

What are challenges you've experienced?

One thing that's always been confusing for me: personal github account vs. organization within the CodeCov UI. I manage my company's CodeCov account - my company has multiple repos using CodeCov, but I have no personal repos using CodeCov. Often the CodeCov UI will toggle to my personal GitHub Context. It's not always clear when this happens, so I'm frequently left wondering "where did my repos go", "where did my users go", "why does it say I'm not on a paid plan", etc. until I realize the account Context switched. The new Context menu in the top left definitely helps make this more obvious, so nice job there. But it would be even better if the confusion could be minimized further. Some possible solutions could be:

1. Let me choose a default Context so that anytime I log in, or anytime CodeCov has to pick a single Context to render, it shows me the one that is actually useful for me.

   For example, if I'm on the landing page viewing with a Context of "All orgs and repos" (the default when I log in), I see my company's repos in the list so it feels like I'm operating on my organization. But then if I click the "Settings" tab, it automatically switches to my personal Context without warning and I'm left wondering where my team & billing went.

2. Let me disable my personal context - I only ever want to see my Organization's Context within CodeCov.

3. When determining a default Context, favor Contexts that have at least 1 repo over Contexts that have 0 repos.

How do you use the tool today? What parts do you use?

1. Tracking coverage trends over time per repo (love the giant trend chart for this)
2. Identifying coverage gaps to help inform where we should be investing further in automated coverage
3. Managing seat licenses for my team

How could we better help your workflow?

We frequently try to identify the biggest coverage gaps/opportunities. We also consider other aspects like "how valuable is coverage in this area", "how many bugs are we seeing in this area", "will this code be changing anytime soon", etc., but starting with the gap analysis is useful in order to then ask more questions about it. The sunburst chart is helpful here, but for a large repo it can be difficult to hover over all the slices. So I typically use the directory listing instead. The visual "percentage coverage" bars are useful here (in the "Coverage" column of the table), but percentage is relative - if I have 10% coverage on a directory that has 10 lines of code, that's much less of a coverage gap than a directory that has 10% coverage on 10,000 lines of code - but the bar shading makes the coverage look the same for both of those directories. So I wind up sorting the directory table by "lines missed", which tells me where my gaps are in absolute terms. It would be neat if CodeCov could make the absolute coverage gaps more clear in some way. Or maybe you could automatically surface "biggest gaps/risks/opportunities" in some way, like listing the top 10 directories with the most lines missed or similar.

Thanks again for investing further in the UI, and for reaching out for feedback!

[CHSchiaffino]

It would be really nice to have a feature for the coverage display on github repos like a LITE version with a information like this:

Sometimes is kinda weird to have the chart and only numbers makes it weird idk it would be a beautiful way to handle the coverage on comments, really simple.

Thanks for reading :)

[binwiederhier]

I like the UI, but I've had problems with diffs not showing up and login not working across all domains for a while. I made a video to make the issue more apparent to you:

This is for https://github.com/binwiederhier/replbot but it happens on other repos too.

[codecovdesign]

Hello @binwiederhier, @CHSchiaffino, @jonaldinger, @nikiizvorski.
Just wanted to thank you all so much for the feedback! I've been sharing the feedback with the team and identifying next steps for resolving the cited issues and designing/iterating on the UX improvements mentioned! We have a lot of upcoming changes so don't hesitate to drop by with thoughts with new UI rolling out. Thanks again 🙏

[binwiederhier]

Thanks for responding. For what it's worth. Logging out and logging back in fixed that issue.

Another thing I found a little odd is the new(?) diff view where the lines are not fully highlighted anymore, but only marked red/yellow/green on the side. I can't find that view right now, but I do like the old one where the lines are fully green/red much better.

[codecovdesign]

@binwiederhier I think you may still be seeing the current (not new UI). But if you come across it again, could you drop a screenshot of the section/Ui you're describing. 🙏

[codecovdesign]

@nikiizvorski Could you send a screenshot or URL of the UI you are referencing to? I was just trying to identify the issue with our support team and wasn't able to. 🙏

[ljharb]

I added this project: https://app.codecov.io/gh/import-js/eslint-plugin-import/ but it isn't showing up on https://app.codecov.io/gh?search=import, despite re-syncing multiple times.

(unrelated, the default branch still seems to default to "master" despite github a) reporting this info in their API, and b) changing the default on new repos to "main" awhile ago)

[AlekSi]

/settings/yaml page prompts me to create codecov.yml file while I already have .codecov.yml that should be okay.

[markhm]

I would like to suggest to start the sunburst graph at the folder level that contains the first actual code file.

Currently, our sunburst graph starts at src/, while our code starts at src/main/java/nl/appname/. To get the richer perspective, we now first need to click.

[Arnie97]

I would prefer the full line background highlight (in the old UI) instead of a narrow colored gutter on the left. May I please have a chance to get it back?

---

In some rare cases, the page margins in the new file viewer are totally lost. I think it would happen if the browser was maximized on an exactly 1280px screen.

Most of the time, the page components flows responsively on resizing of browser window. The following screenshot shows one little bad case.

[codecovdesign]

@Arnie97 thank you for your feedback! It's greatly appreciated and very helpful.

I would prefer the full line background highlight (in the old UI) instead of a narrow colored gutter on the left. May I please have a chance to get it back?

Yes. The file viewer will soon be seen on the commit details and later on the compare page. As the new UI is released there will be a toggle to view the old UI, while we finalize the new UI transition and collect feedback like this for improvement.