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.

[ghost]

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.

[webknjaz]

Dunno if it's related to your web app update effort but the coverage reports stopped being processed a day or two ago: https://community.codecov.com/t/error-processing-coverage-reports-with-github-actions/3251/4?u=webknjaz. FYI.

[webknjaz]

That turned out to be a bug in the uploader (codecov/uploader#413 / codecov/uploader#411).

Meanwhile, here's a legit new UI bug: CI job links in the Uploads block are non-clickable (the <a> tag is there but there's no href= specified).

[codecovdesign]

@webknjaz Thank you for you note!
Followed up with our engineer team and we are actively working on resolving the issue. The former UI is available from the toggle seen in the banner. We will keep this will we continue to release the new UI.
Again, appreciate the report, and if you see anything else or other feedback about the new UI, please let me know 🙏

[vinniefalco]

I can honestly say that never, in my entire 39 year career of writing software have I ever thought to myself "I wish they would present this information in TWO columns side by side and make the view of my source code more narrow:"

[vinniefalco]

[vinniefalco]

Microsoft did the same thing to GitHub when they "improved" their UI. They took the title, description, and hyperlink for my project which used to be at the top above the fold, clearly visible and without being truncated - and moved it to the right side in its own narrow column where it is wrapped heavily and with the link truncated (and with the title removed).

[dpelle]

In the new UI, the source code is not being displayed with correct indentation anymore when source code uses tabs rather than spaces.

I see this problem e.g. with Vim.

It seems that source code is shown as if tabs counted as 4 spaces whereas the default for tabs is traditionally 8 spaces.

Screenshot showing bad indent in CodeCov:

Notice how code inside the 'if' blocks at line 806 or 812 is badly indented. It's messy.

Same source code properly indented in Vim:

The grey »… in Vim show tabs.

[webknjaz]

have I ever thought to myself "I wish they would present this information in TWO columns side by side and make the view of my source code more narrow:"

TBH code is text. And text is most readable in narrow columns, that's why newspapers and magazines don't do edge-to-edge lines — it's weird and makes your eyes jump from side to side. (see also: typography)

But it may indeed be reasonable to make the representation more centralized rather than just shifted to the right. Or maybe add an ability to collapse the left column, or introduce some sort of a "Zen mode".

[ljharb]

If that were universally true, books would have multiple columns too. Newspapers optimize for something different than code viewers need to.

[webknjaz]

Books do this too. If it's just "one column", they just adjust the font size or margins not to exceed the maximum readable character length (between 45 and 75 chars).

[ljharb]

Then i think we’ve read very different sets of books :-)

[codecovdesign]

@dpelle Thank you for the feedback, it makes sense. Our team is looking at improving this with upcoming iterations.

[codecovdesign]

👋 @webknjaz @ljharb @vinniefalco Thank you for sharing feedback and different perspectives on the new UI. It helps our team as we are weighing the different tradeoffs for iterations along the way. In the interim, the former UI is still the default and available while we finish releasing and updating all new pages.

And text is most readable in narrow columns, that's why newspapers and magazines don't do edge-to-edge lines — it's weird and makes your eyes jump from side to side. (see also: typography). But it may indeed be reasonable to make the representation more centralized rather than just shifted to the right. Or maybe add an ability to collapse the left column, or introduce some sort of a "Zen mode". they just adjust the font size or margins not to exceed the maximum readable character length (between 45 and 75 chars)

💯 @webknjaz I like this! Another thing we are considering for improved code viewer readability: is having a fluid layout (user can toggle either fluid or fixed). The example below shows a fluid version; which aims to optimize the whole available browser window, while also showing all the elements in space and not time (data hidden behind tabs). Again, the user could toggle in settings between the fluid or fixed. wdyt?

[webknjaz]

@codecovdesign that sounds reasonable.

One comment, though: the "Uploads" block is not essential in this view, normally I only need it if something goes wrong and I'm trying to figure out if some reports didn't reach Codecov. I don't imagine any other use-cases. That said, I'd maybe show it on request but not by default. OTOH this empties up a lot of space depending on the height of the code section. Which would be fine in a one-column view with equal margins on both sides keeping that content easy to focus on without distractions. In case, when the uploads are not shown, the "Coverage report" block may make sense to be relocated on top of the file content view (and made less tall). I mean, of course, the overall coverage is the most important piece of info about the commit but I've probably seen it before navigating to the commit details page and want to focus on finding out the reason behind the drop or other data, right?

[vinniefalco]

In the interim, the former UI is still the default

it isn't though, the green highlight does not extend across the line, only in the gutter.

[rouilj]

@rouilj thank you for the detailed and thoughtful feedback!

NO reason that the list view shouldn't display a thousand or more lines in list view

~I'm surfacing this with the eng team for feedback about any potential loading issues for larger repos.
We agree with the load more, as it is temporary from the initial iteration on this section.
~ EDIT: confirmed to show all without and loading/pagination ✅

One thing I took out of original comment because it was getting too long and adding nuance wouldn't help.
If the user's browser sends the Save-Data header or css prefers-reduced-data is enabled, paging is perfectly reasonable. I suspect that people who are viewing the site aren't on mobile devices with limited data plans. But you have the stats so I'll leave that for you to investigate.

I would still claim that allowing the user to choose the default number of lines in the top UI of the table
for list view would be useful in supporting the non-"Table of Contents" use case. But at least showing all lines
won't break one of my original 2 use cases.

[rouilj]

@vinniefalco, understood.

I know about gallows humor. I am currently working as an EMT. Have been once since college in the 80's.
Gallows humor abounds.

[AJenbo]

I miss the sun diagram on the main page, it gave a good overwrite of project coverage, instead now I just have 2 folders in a list that i have to drill in to/get lost in, not very informative.

The flags feature is presented in a way that makes it appear critical but I have both had trouble enabling it and concluded that its not actually relevant for any of my projects.

I also miss delta from the commits/pr page, it now only shows total and diff (the new way of presenting them is easier to understand)

[AJenbo]

The new time line graph that is presented instead of the sun diagram also doesn't scale to the content with makes it kinda ussels for some projects:

I realize that it allows scrolling, but to call that intuitive is an understatement. X and Y scroll at the same time, and its happy to place you somewhere outside the data

[caendesilva]

I primarily use Codecov for insight on pull requests (now that the sunburst is removed for some reason) and what really bothers me and still surprises me every time I try it is that the impacted files all lead to the same page. What's the point of making all the file names clickable if the page they lead to is useless? Each time I think that when I click on a file that's missing coverage I will be taken to a page showing me information about that file. And each time I'm disappointed.

[vinniefalco]

Is the ability to get to the Files view for a particular branch gone now? Removing "app" from the URL no longer works and I am stuck on this screen:

[rouilj]

Hi Vinnie:

It looks like you are viewing a pull. Have pulls and commits ever have a branch selector?

I only remember it at the top repo level, but I might be mistaken.

If it was there, it would have to take you back to the top repo level since a pull or commit is only applicable to a single branch right?

Oh I think I see what you mean: The old view had:

  Overview Commits Branches Pulls Compare

menu items in all screens. And yes, branches jumped you out of commits/pulls.

Commits still has the branch selector as well as Coverage in the new app. But you can't get there without
clicking on the json or Pulls link to get to a page where you can choose commits or coverage and access a branch selector.

-- rouilj

[vinniefalco]

Yes I can get to the branch selector but only the branches of the upstream repo appear, not the pull request branch / commits. Yes I used to be able to see the file view for individual pull requests.

[codecovdesign]

@vinniefalco files view is coming to the commit UI in January. Right around the time I'd like to do a follow up walkthrough with you. Additionally, the pulls page will be seeing some updates to better separate diff / indirect changes (later can add files like commits)

Re: the branch selector, can you expand on what you're trying to do and/or ideal state would be?

[vinniefalco]

can you expand on what you're trying to do and/or ideal state would be?

Me? I was just rooting around looking for the files view.

[vinniefalco]

I'm at a point now where I need to look at the coverage report from some new code I'm writing and.... UGH

I copied the URL from the uploader's output:

And this is that landing page:

The screenshot is from my side screen which is 1920x1200 running in portrait, look at how the filenames wrap. UGH. The only thing that looks worse than this is a pair of new Crocs (any color).

I don't like that ridonculous rectangle on the right (the one that shows the "Uploads 2 successful")

OK so I'm a team player I try to click on the file of interest, header.ipp and are you forking kidding me, it expands in place? Jesus H....

Broseph I DO NOT want to expand in place I want to view the file in a new tab, side by side with other file coverages!

Okay so lets do the standard right click "Open in new tab" or the good old CTRL+click (in Chrome). NOPE That doesn't work, it just opens a new tab to the same page. Can you please give me the names and the LinkedIn pages of the people that are responsible for choosing to make it work this way? How can I put it...

QUITE FRANKLY, THIS SUCKS

The more I see the more I am convinced that the problem is not with the web application itself but this is rather a staffing problem...

OH my god... wtf.. I can't even... You really? You really? You really WORD WRAPPED MY SOURCE CODE and screwed up all of my dividers and carefully manually-wrapped javadocs?

This is a comedy of design mistakes, one leads to another (obviously you are trying to avoid a horizontal scroll bar in the roll-down of the source file). Hint: go back to how it was, replace the design team with people who know what they are doing.

Apologies for being so blunt but we are very late in the game and there is no time to mince words. Look at the date on when this issue was opened:

So in 18 months all we have accomplished is to make the entire experience worse, with no signs of changing course to making it better? Every time I check back here something is worse...

[vinniefalco]

To be completely fair, this is at least an improvement:

[codecovdesign]

@vinniefalco thank you for your feedback. Specifically your points about screen sizing, inline scrolling, expand view, open new tab (not sure why that'd not work) are all very helpful and we're on it.

I invite your feedback and it's greatly appreciate it, but disparaging comments about our teammates are not acceptable - please stop. We have a dedicated team that is working hard daily to iterate and improve the app.

[antifuchs]

Echoing the desire for a list of all files on the pull request view. I've got a (flakey, probably) test on a pull request that's listed as -0.1%, which won't let me merge the patch - but all of the files that changed in the PR have 100% coverage. So the change is somewhere outside that pull request, but currently it's impossible to find in which file the coverage change happens.

If the codecov backend has information about what files have seen any change to coverage at all, it would be very useful to show all of those files too, even if there were no code changes made to them in the pull request.

[AJenbo]

OMG it's back, I love you <3

[vinniefalco]

My team is putting the finishing touches on a beautiful new set of report templates for gcov which replicate the original codecov interface experience. If anyone has screenshots of the original source file view, source file view with commit diffs, source file view with coverage diffs, and source file view with total coverage or knows where to look to find them please message me (email in my GitHub bio) - these templates will be free and open source.

[vinniefalco]

Also, I've been gone for quite a few months and I'm somewhat pleased to see unequivocal improvements to some of the previous issues; However there are still elements which need work.

[codecovdesign]

@vinniefalco 👋

new set of report templates for gcov

Nice! Looking forward to seeing the results – I'll email you a few screen shots I have.

there are still elements which need work

Indeed. Would love to jump on a call and walkthrough your thoughts further. I'll add invite to my email to you.

Lastly, we will be closing this issue soon. We'll be setting up a new repo to add issues and feedback - more on this topic coming soon - in the interim we do have a feedback forum.

[vinniefalco]

Logging in to my account.

List of orgs and repos this seems OK:

Scrolling down a bit, ok now things are getting weird. The organizations are not sorted? Oh, I get it, I guess... they are sorted by repository name. But wait that can't be right, they are sorted by "last updated." Oh I can't change the sort by clicking on the column. Whatever, its just the repository list who cares.

Oh well, "about 1 month ago" is wrapping. Now the row is larger so list items are not evenly spaced:

That is unfortunate because I do feel like my windows is pretty wide... surely we can fit everything in there without the need to wrap?

Well lets click on one of the repos. This seems inoffensive at first glance:

Wait a sec what's with the baseline of the branch name text not aligned vertically with the rest of the path?

Ooops, another unaligned baseline. Seems to be a common theme, two pixels off here:

Now, the green background of this text is not wrong per se, but it is not aesthetically pleasing, because the characters butt right up to the edge:

You could throw a space before and after that text, and it could look like this:

I would go with a rounded corner rectangle myself since it goes with the new font you chose (which I hate):

[vinniefalco]

There's a general problem where when you click on things the entire new page shifts left, right, up, or down after the reload. When a user navigates, interface elements should not move. Especially the top navigation, that thing needs to be solid like a rock:

When I navigate this top nav is hopping around like Jiminy Cricket

[codecovdesign]

@vinniefalco thanks for sharing this feedback!

organizations are not sorted? Oh, I get it, I guess...

Agreed, it should indicate what the sort is! You'll notice some headers have the sort ability – there is a th bug we are fixing there to display it by default across all table component.

"about 1 month ago" is wrapping
entire new page shifts left, right, up
with the baseline of the branch name text not aligned vertically
unnaligned baseline. Seems to be a common theme

Noted - will investigate...what browser are you using?

could throw a space before and after that text

agreed, great suggestion!

rounded corner rectangle myself since it goes with the new font you chose (which I hate)

I was hoping you'd noticed that our numerals on the tables are Lato (tabular) - our OG font / your preference 😢

@vinniefalco thanks again for the report 🙏

[vinniefalco]

Those are all I looked at but I will look at the other pages soon

[kupka]

I'm still a bit confused about the numbers displayed on a PR such as these:

https://app.codecov.io/gh/kupka/libsrd5/pull/27

I get it that the -0.04% is the difference between main (100%) and the branch head (99.96%). However, placing the -0.04% after the 99.96% (head) and 99.54% (patch) makes me always feel that this is basically flawed arithmetic.

I still haven't figured out what the "patch" value in this case means, especially when the only file that has missed lines looks like this:

With head% and patch% both at 96.59%. All other files are displaying head/patch at 100% so I don't really get the difference with the numbers on top.

[codecovdesign]

Hello 👋

Thank you for all the contributions and great feedback in this issue. We are closing this issue, but would love your feedback here:

• General feedback and feature request
• Experience setting up your repo with Codecov
• Pull request comment
• Flags section/features
• Impact analysis (alpha) feature

🙏

[prensjr]

Thanks for your support, surly your advice and help is needed as am newbee too.

[vinniefalco]

The C++ Alliance has sponsored Frank Wiles' work to add customizable templates to gcovr. This will allow for more profound customizations than before, using stock gcovr. It is our goal to produce templates similar to how codecov used to look before the UI was "improved." You can see that work here:
gcovr/gcovr@87634c1