Screen recording can be a super helpful thing to debug why a test failed. However, right now one needs to manually activate them for every flow by using the startRecording and stopRecording commands which leads to boilerplate.
Proposal
Provide a way to toggle screen recordings for all flows, e.g. via a command line parameter --enableScreenRecording. The names of the mp4 files could be automatically deducted from the test file, e.g. test1.yaml -> test1.mp4.
As an extension of this, and potentially even more useful, there could also be another flag which would enable storing of recordings just for failed tests, such as --enableScreenRecordingOfFailedFlows, to help preserve system storage.
Use case
Screen recording can be a super helpful thing to debug why a test failed. However, right now one needs to manually activate them for every flow by using the
startRecordingandstopRecordingcommands which leads to boilerplate.Proposal
Provide a way to toggle screen recordings for all flows, e.g. via a command line parameter
--enableScreenRecording. The names of the mp4 files could be automatically deducted from the test file, e.g.test1.yaml->test1.mp4.As an extension of this, and potentially even more useful, there could also be another flag which would enable storing of recordings just for failed tests, such as
--enableScreenRecordingOfFailedFlows, to help preserve system storage.Anything else?
No response