Is your feature request related to a problem?

When running on multiple devices in parallel, some devices will run the tests using the same browser which makes it difficult to tell the individual devices apart.

[1] [5-0] RUNNING in chrome - file:///C:/.... --> (Android)
[1] [3-0] RUNNING in safari - file:///C:/.... --> (iPhone)
[1] [1-0] RUNNING in Edge - file:///C:/....
[1] [0-0] RUNNING in chrome - file:///C:/.... --> (Windows Desktop)
[1] [4-0] RUNNING in safari - file:///C:/.... --> (iPad)
[1] [2-0] RUNNING in Safari - file:///C:/.... --> (OS X)

Looking at the ouput, it is not possible to determine what device the test is running, only the kind of Browser. Safari is being used on three different devices (OS X, iPhone and iPad) but since browserName is the only identifier, it's hard to tell the different devices appart.

Describe the solution you'd like.

There are in my opinion numerous ways of making this more readable.

If i log the browser, several interesting things comes out. For desktop devices, the thing to use is probably platformName. This come with a problem though: if you run your tests in parallel on multiple OS X versions using Safari, they will still come out as:

[1] [1-0] RUNNING in safari on mac- file:///C:/....
[1] [2-0] RUNNING in safari on mac- file:///C:/....
[1] [3-0] RUNNING in safari on mac- file:///C:/....
[1] [4-0] RUNNING in safari on mac- file:///C:/....

I suppose browserVersion could be added aswell for desktop devices:

[1] [1-0] RUNNING in safari 18 on mac- file:///C:/....
[1] [2-0] RUNNING in safari 17 on mac- file:///C:/....
[1] [3-0] RUNNING in safari 16 on mac- file:///C:/....
[1] [4-0] RUNNING in safari 15 on mac- file:///C:/....

If you are running your tests on a mobile device, you should be presented with deviceName (e.g = iPhone 14). That would at least make it possible to differentiate OS X from iOS devices:

[1] [1-0] RUNNING in safari on mac- file:///C:/....
[1] [2-0] RUNNING in safari on iPhone 14- file:///C:/....
[1] [3-0] RUNNING in safari on mac- file:///C:/....
[1] [4-0] RUNNING in safari on iPhone 12- file:///C:/....

The same problem could appear here aswell if you are running tests in parallel using different OS versions with the same device:

[1] [1-0] RUNNING in safari on iPhone 14- file:///C:/....
[1] [2-0] RUNNING in safari on iPhone 14- file:///C:/....
[1] [3-0] RUNNING in safari on iPhone 14- file:///C:/....

Describe alternatives you've considered.

Honestly: the best way to fix this would be to print the information the same way as the spec reporter does:

[Safari 18.4 mac #1-0] Running: Safari (v18.4) on mac
[chrome 138.0.7204.50 Windows 11 #0-0] Running: chrome (v138.0.7204.50) on Windows 11

If that's not possible, I would suggest the solution provided above.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct