microsoft / microsoft/playwright

[Feature]: Either deduplicate the badge when tag and project name are the same string, or visually distinguish project badges from tag badges (e.g. different color, shape, or prefix).

Open
#40,938 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P3-collecting-feedback
Dominant language
TypeScript
Stars
96.3k
Forks
6.5k
Avg merge
1d 6h
Merged PRs (30d)
180

Description

### 🚀 Feature Request

Describe the bug / UX issue:
HTML reporter shows duplicate badge when tag name matches project name

When a test's tag matches the project name (e.g. project ad2 and tag @ad2), the HTML report renders two identical badges side by side — one for the project, one for the tag. There's
no visual distinction between them, making the duplicate confusing and redundant.

Image

### Example

To reproduce:
// playwright.config.ts
{ name: 'ad2', grep: /@ad2/ }

// spec file
test.describe('My suite', { tag: ['@ad2'] }, () => { ... })
Run with --project ad2 → report shows ad2 ad2 badges on the test row.

### Motivation

Expected behavior:
Either deduplicate the badge when tag and project name are the same string, or visually distinguish project badges from tag badges (e.g. different color, shape, or prefix).

Playwright version: 1.60.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the HTML reporter by reproducing the issue using a project named ad2, a @ad2 tag, and the --project ad2 run described here. Inspect how project and tag badges are rendered, then verify that identical badges are either deduplicated or visually distinguished in the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
testing
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.