[Bug]: Results of test run in UI Mode disappear after short delay with "Did not run" message

[karlhorky]

Version

1.43.0

Steps to reproduce

1. Run a test using UI mode (playwright test --ui)
2. After test errors or is successful, the results disappear with the message "Did not run" 💥

Kapture.2024-04-17.at.20.44.53.mp4

Expected behavior

The test results shouldn't be cleared / disappear

Actual behavior

The test results disappear

Additional context

No response

Environment

System:
    OS: macOS 14.4.1
    Memory: 138.88 MB / 16.00 GB
  Binaries:
    Node: 20.12.2 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.5.2 - /opt/homebrew/bin/npm
    pnpm: 9.0.2 - /opt/homebrew/bin/pnpm
    bun: 1.1.4 - /opt/homebrew/bin/bun
  Languages:
    Bash: 5.2.0 - /opt/homebrew/bin/bash

[karlhorky]

Oh, looks like @dtokarczyk reported this same issue over in #30339 and @mxschmitt fixed in #30312 🙌

I can confirm that @playwright/test@1.43.1 fixes the issue for us.

Closing

[VisualFinesse]

I'd like to open this ticket back up since I'm getting this exact error in 9.6.7

[TobiasMende]

I have the same issue with Playwright 1.46.0. – Can you reopen this issue @karlhorky or shall we create a new issue?

[TobiasMende]

Update: I found the reason for this behaviour by running the suit without the --ui flag. In my case, I had a duplicate test name. This error leads to this behaviour without any warning/notification.

[karlhorky]

@TobiasMende I cannot reproduce yet on 1.46.0.

Can you first confirm that it is the exact same behavior that is shown in the video?

Eg.

1. Test runs
2. Results are shown
3. Results disappear after short delay
4. "Did not run" message is shown

Then if you can create a video confirming this for 1.46.0 (eg. with Loom or ScreenToGif (Windows only) or Kap (macOS only)) and post it here (make sure to show the version number and the behavior), then I will reopen.

[TobiasMende]

@karlhorky sure thing. I have recorded a small video to demo this (in the audio I explain it, as well)

GMT20240809-090000_Clip_Playwright.Duplicate.Name.Bug.mp4

If you want a minimal example:

1. Create a suite inside a file that has two tests with the same name.
2. Create other tests in the file

The behavior with Playwright UI for me is: After I ran the suite with the duplicate name in it, I get the above behaviour. After that, no other tests can be executed.

Hope this helps. :-)

[karlhorky]

Nice, thanks for taking the video - it's pretty close to the behavior!

It's missing the key points 2. "Results are shown" and 3. "Results disappear after short delay" though - so probably good to open a separate issue for that.

[TobiasMende]

Ah you are right. Here is the new issue: #32093

[WarrenMfg]

Duplicate browsers in the config's projects array will also demonstrate similar behavior.