[Feature]: Filter options in the trace viewer to filter recorded actions

[Westermensch]

🚀 Feature Request

As a user story:

As a developer
I want to filter the actions shown in the actions tab of the trace viewer
So that I can find the actions i want to debug more efficient.

Example

Example test:
Given I loaded a trace file into the trace viewer
When i set the action-filter to "locator.click"
Then i can only see click-actions in the action tab of the trace viewer.

Motivation

For long running traces, the actions tab can get very hard to read, expecially when you have plenty of actions that are not that interesting for the actual test workflow.

Also having the option to filter the actions to specific types, could make the trace more readable for non-developing stake holders.

[Skn0tt]

Hi there! I'd like to understand more about your usecase.
Are you checking the trace to see why a test went wrong, or is it for verifying a long running automation job? When you say "long running", how many actions is that and how long is the duration?

[Westermensch]

Thank you for the fast reply :-)

In my specific use case, the trace is of a system level test, and is about 5 minutes of interaction with the web ui of the application.
In the actions list, we have probably hundrets of actions, most of them are only relevant for developers, eg (locator.evaluate, page.waitFor) as they are not directly linked to a user-interaction. Now when a stake holder, for example a Product-Owner, wants to inspect the trace files, they are mostly interested in user-oriented actions, eg (locator.click, page.screenshot) and it would help them a lot if they could set a filter to only see the actions they are interested in.

[Skn0tt]

I see, thanks for elaborating. Let's collect some upvotes to gauge community interest.