You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, when using the Browser library in Robot Framework, the recording video is attached to the keyword that opens the browser page. However, in most cases, we only need to check the video when a test fails.
When a failure occurs, we have to manually locate the New Page keyword to find the corresponding video clip, which is inconvenient.
Especially in a messy steps report, it's pretty hard to locate it immdiately.
Describe the solution you'd like
Introduce a keyword that allows users to retrieve the video clip dynamically based on the page ID or other filters.
Example:
Get Page Recording Video page=${pageId}
This would let users fetch the video during error handling, similar to taking a screenshot, making it easier to access the relevant recording directly in the test report.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, when using the Browser library in Robot Framework, the recording video is attached to the keyword that opens the browser page. However, in most cases, we only need to check the video when a test fails.
When a failure occurs, we have to manually locate the New Page keyword to find the corresponding video clip, which is inconvenient.
Especially in a messy steps report, it's pretty hard to locate it immdiately.
Describe the solution you'd like
Introduce a keyword that allows users to retrieve the video clip dynamically based on the page ID or other filters.
Example:
Get Page Recording Video page=${pageId}
This would let users fetch the video during error handling, similar to taking a screenshot, making it easier to access the relevant recording directly in the test report.
The text was updated successfully, but these errors were encountered: