-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable video recording on cypress run #867
Comments
You can already disable video recording with proper configuration in your cypress.json file (doc) : You can also do it with CLI by overriding your Edited by @jennifer-shehane to update key |
@MarcLoupias Thanks! Not sure how I missed that. |
Thanks everyone for this issue as I ran into it as well. However, I do have some thoughts here on usability (but maybe my expectations are wrong):
Doing it via config override totally does the trick, it's just less comfortable and to be honest, I didn't run into the overriding docs when searching for such a feature. Frankly I didn't actually search for "overriding config" but rather "how do disable video recording in Again, my expectations may be wrong here. I'm just leaving it here as feedback :) |
@PascalPrecht There's another issue open that talks about how "recording" and "video recording" is confusing nomenclature. What it's really saying is two different things. By default Cypress takes a video of the run without any flags -- thats the video recording feature. You can turn that off with configuration or CLI flags. |
The
|
hahaha @brian-mann we posted together! |
@PascalPrecht here's the other issue for reference #562 |
Thanks for the clarification! This all makes total sense. I assume tho then, that this has potential for improvement. Not sure if I'm the only one who got confused by this. |
|
For the “record”, it is still videoRecording in 3.0.1 . |
Hey @aries1980, what key are you referring to? Where are you using the If you were to use the
|
It's still |
I created a new issue in our docs to document the incorrect key reference here: cypress-io/cypress-documentation#1030. Our documentation is open source and contributions are welcome. 😄 |
Thank you. @jennifer-shehane :) |
|
@jennifer-shehane, @MarcLoupias is there any possibilty to record video for only failed specs not for passed test cases and used them in report if any test suite fails due to any test case. Thanks. I hope you got my point. |
@KhizerRehan There is no way to only record video for 'failed' specs because we don't know what will fail or pass until the tests are over and the recording is done. You can delete the videos for passed specs though with this code: https://on.cypress.io/after-spec-api#Delete-the-recorded-video-if-the-spec-passed |
I believe what others and myself are looking for is a way to opt out of sending anything to the dashboard in the event that all tests pass, as this is what counts against the dashboard usage quotas. I have absolutely no use case for reviewing passed/successful runs on the dashboard, they just burn through the dashboard allocation/quota. |
@jennifer-shehane Is it possible to rerun a test case with video recording on failure? If the test case is successful we can just pass it without recording, if possible this will definite fast up our CI. |
If a test fails, you could run the test again and record it that time. |
I write a blog post about this https://onebite.dev/disable-video-recording-when-running-cypress/ with other information regarding video recording TLDR;
in your cypress setting |
I found that CYPRESS_video=true cypress run |
Current behavior:
Video recorded on every
cypress run
.Desired behavior:
CLI and/or config option to disable video recording on
cypress run
.How to reproduce:
Run
cypress run
. See "Started video recording" message and generated video file incypress/videos
.Additional Info (images, stack traces, etc)
I'm not using the videos while developing and I'd rather save the time/processing and lower my chances of running into associated bugs by disabling this functionality altogether when I need to run all tests.
The text was updated successfully, but these errors were encountered: