[🚀 Feature]: Additional information (columns) in Sessions

[adrian-tarau]

Description

It would be nice to see client-specific information in the sessions view in Grid. Currently, you see the Session ID (which is only useful for troubleshooting), Capabilities, Start Time, Duration, and node URI.

In most cases, the following information is available when a test runs:

• Project Name: The project runs the tests
• Feature: The feature (Cucumber, etc) or Class Name (or the Display Name for JUnit5/etc.)
• Scenario: The scenario (Cucumber, etc) or Method name (or the Display Name for JUnit5/etc.)

With all these three pieces, looking at what runs in the grid will tell you which one to examine (if you have VNC enabled).

It could be under a new namespace or se namespace, like this:

• se:project
• se:feature
• se:scenario

Have you considered any alternatives or workarounds?

No response

[selenium-ci]

@adrian-tarau, thank you for creating this issue. We will troubleshoot it as soon as we can.

Selenium Triage Team: remember to follow the Triage Guide

[adrian-tarau]

I looked at the code, and I think I can provide a PR. But I would still need to know what the attribute names to be used to store those three attributes.

[VietND96]

Caps with the prefix se: are defined by the user.
In my view, I prefer an implementation where user is able to add a new column with provide a capability key name to extract from info and show to that column (dynamic set, instead of set static column)

[selenium-ci]

This issue is looking for contributors.

Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.

[adrian-tarau]

Indeed, being configurable is a plus. However, in the absence of a configuration (for session columns), it would be nice to have a default. Showing those three columns with a "-" would tell any user that that information could be provided (also described in the Help page as the standard capabilities used to populate those columns).

[VietND96]

@adrian-tarau, can you review the implementation detailed here #15759

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.