Version
1.58.2
Steps to reproduce
Have a describe block and a nested test both tagged with the same tag eg
test.describe("@saas tests tearsheet", () => {
test("@saas create HTTP test using tearsheet", async ({
Expected behavior
HTML reporter should only show the @saas tag once
Actual behavior
saas is here 3 times. Once because its in a project called saas, and then two more times. Once for the describe and then once for the test. I would expect the describe and test tags to be collapsed to one.
Additional context
The tags in the test names already eats up a lot of screen real estate (see #17375) and now showing multiple of the same tag pills eats up even more.
Do I have a usecase for having the same tag in the describe() and test()? Not really, this is just a huge suite with a lot of things that have moved around over the years, so I recognize this scenario may not be all that common.
Environment
System:
OS: macOS 26.3.1
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 56.99 MB / 32.00 GB
Binaries:
Node: 24.15.0 - /Users/seanlafferty/.nvm/versions/node/v24.15.0/bin/node
npm: 11.12.1 - /Users/seanlafferty/.nvm/versions/node/v24.15.0/bin/npm
pnpm: 10.33.0 - /Users/seanlafferty/.nvm/versions/node/v24.15.0/bin/pnpm
Deno: 2.5.2 - /usr/local/bin/deno
IDEs:
VSCode: 1.113.0 - /usr/local/bin/code
Languages:
Bash: 3.2.57 - /bin/bash
npmPackages:
@playwright/test: 1.58.2 => 1.58.2
Version
1.58.2
Steps to reproduce
Have a describe block and a nested test both tagged with the same tag eg
Expected behavior
HTML reporter should only show the
@saastag onceActual behavior
saasis here 3 times. Once because its in aprojectcalled saas, and then two more times. Once for thedescribeand then once for thetest. I would expect thedescribeandtesttags to be collapsed to one.Additional context
The tags in the test names already eats up a lot of screen real estate (see #17375) and now showing multiple of the same tag pills eats up even more.
Do I have a usecase for having the same tag in the
describe()andtest()? Not really, this is just a huge suite with a lot of things that have moved around over the years, so I recognize this scenario may not be all that common.Environment
System: OS: macOS 26.3.1 CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz Memory: 56.99 MB / 32.00 GB Binaries: Node: 24.15.0 - /Users/seanlafferty/.nvm/versions/node/v24.15.0/bin/node npm: 11.12.1 - /Users/seanlafferty/.nvm/versions/node/v24.15.0/bin/npm pnpm: 10.33.0 - /Users/seanlafferty/.nvm/versions/node/v24.15.0/bin/pnpm Deno: 2.5.2 - /usr/local/bin/deno IDEs: VSCode: 1.113.0 - /usr/local/bin/code Languages: Bash: 3.2.57 - /bin/bash npmPackages: @playwright/test: 1.58.2 => 1.58.2