-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Ability to record *.gifs #1511
Comments
+1. This would be nice a feature from cypress. |
Great idea! As a further enhancement, it would be nice to gif on a selector, so that I can see the animation for one component and minimize file size and extraneous information when I send to a teammate. |
You should be able to grab the path of the created video using the Module API and transform the video yourself into a |
This feature will help a lot in terms of debugging. If cypress provides a callback to transform video to gif would make reporting analysis easier. @jennifer-shehane @brian-mann @bahmutov - Thoughts? |
This is a good suggestion @rsudarson and I plan to implement something like this in bahmutov/cypress-movie#10 |
This may be useful to view test results in VS Code. So, gifs are the way to go |
GIF's are also a neat way of communicating usage to customers. However it's worth noting that ffmpeg should (at least in theory) be able to output gifs. Will get back to you if I actually manage to do this. |
Is this a Feature or Bug?
Feature request!
Current situation:
Currently we've got a possibility to record and save videos from test runs, which is really great! But many times QA's have to report a bug which is very hard to describe, e.g. animation behaving somehow wrong, weird UI jumps, etc.
Desired feature:
I would love to see a possibility in a test run to be able to save a *.gif file for chosen steps, so that I can easily and fast explain wrong behavior of UI for my dear developers.
Additional Info (images, stack traces, etc)
Very good work on cypress though. I am impressed!
Anyone sharing the same opinion?
The text was updated successfully, but these errors were encountered: