Discussion: HTML coverage report layout (Statement/Branch columns and excluded column) #2081

Summary

This issue is to discuss potential updates to the HTML coverage report layout.

From recent conversation, two related points came up:

1. Displaying Statement Coverage and Branch Coverage as separate columns

• This could make it easier to visually notice when one metric is falling behind the other.

2. Reconsidering the excluded column

• The excluded column may not provide meaningful value for many users.
• It is shown only for statements, with no corresponding column for branches.
• This creates an asymmetry in the UI.

Proposal

Discuss the HTML report layout as a whole:

• Add separate Statement and Branch coverage columns.
• Remove or relocate the excluded column to improve clarity and consistency.

Goal

The goal is not to decide immediately, but to gather feedback from maintainers and users to determine which layout is most clear and useful.

Looking forward to hearing your thoughts.