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
If you're recording with videoCompression set to some number (other than 0), a section for Video output is displays to the terminal like shown below. This information contains progress around compression time and time it takes to process the video in general, but it also includes a link to the video which is valuable to see where the video is recorded.
If you turn off videoCompression, setting it to false - this entire section is not printed. So you can't see the location of the recorded video. There was a recorded video below, but no one would know.
Current behavior
If you're recording with videoCompression set to some number (other than 0), a section for Video output is displays to the terminal like shown below. This information contains progress around compression time and time it takes to process the video in general, but it also includes a link to the video which is valuable to see where the video is recorded.
If you turn off videoCompression, setting it to false - this entire section is not printed. So you can't see the location of the recorded video. There was a recorded video below, but no one would know.
Desired behavior
This line of code, as well as the Video section title itself should still print when videoCompression is set to false. https://github.com/cypress-io/cypress/blob/develop/packages/server/lib/util/print-run.ts#L540
This isn't happening because this entire section of printing in only ocurring if there is progression in processing the video. Really the link to the video should be separated out into a section that's always printed when video is present. https://github.com/cypress-io/cypress/blob/develop/packages/server/lib/video_capture.ts#L371:L371
Test code to reproduce
Run the code below in any project.
cypress.config.js
Cypress Version
12.5.1
Node version
16.16.1
Operating System
Mac
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: