Creating Screencasts
You’re free to choose any tool to create screencasts. It’s important, that you provide a .mp4 video of appropriate quality (resolution and presentation). Common browsers should be able to play your video.
Your screencast should only show the action that triggered the reported bug in all situations and you should add the last few steps to reproduce if it's a bug report (usually adding 10 seconds to the video at most). Also, screencasts that are longer than 1 minute for Bug Reports and 15 seconds for Reproductions and User Stories will not be accepted unless they are really necessary to understand the bug or the video is long because of variables you can't control (such as a slow website response).
You should have your device sounds switched off unless required to understand the issue. Room noise such as other people's conversations, ambient music or animal sounds should not be recorded at all.
Suggested tools for desktop devices
Screencast-O-Matic (free)>> http://screencast-o-matic.com
Windows & Mac OS
Videos can be created as .mp4 files
Up to 15 minutes per video
Has an integrated mouse effect animation to show clicks
Optional upgrade with more functions
The free version leaves a watermark
Bandicam (free)>> https://www.bandicam.com/
Windows only
Videos can be created as .mp4 files
Has an integrated mouse effect animation to show clicks
Optional upgrade with more functions
The free version leaves a watermark
Open Broadcaster Software (free)>> https://obsproject.com/
All features are accessible for free
Windows & Mac OS
Might not work on older computers
Can be a bit challenging to set up for the first time
Leaves no watermarks
You must use additional software to show the mouse clicks
Find a video tutorial here:
https://www.youtube.com/watch?v=DTk99mHDX_I
Suggested tools for mobile devices
Built-in screen recorder (Android 11+ and iOS 11+)
No need for third-party apps
Good video quality
On iOS, you might need to navigate to Settings > Control Center, then tap the Add button next to Screen Recording to enable this option on the Control Center menu
On Android, the screen recording button can be found on the Notification Bar
Note: For iOS, you must convert the .mov files to .mp4. You can use an online converter such as https://www.mp4compress.com/mov-to-mp4-converter/ or any offline converter, such as HandBreak (available here: https://handbrake.fr/).
AZ Screen Recorder (free, Android only)
>> https://play.google.com/store/apps/details?id=com.hecorat.screenrecorder.free
Records in different resolutions and qualities
You can use your mobile IP local address to access the files wirelessly using a desktop device
You can stop the recording using different methods
Mobizen (free, Android only)
>> https://www.mobizen.com
Can be a bit complex to set up for the first time
Records in different resolutions and qualities
You must either buy the premium app or watch a small ad to remove the watermark
Available in many languages
Alternative: Record your bug with a second device or an extra camera! Just remember to frame the entire device screen correctly while recording the video.
Note: videos must not be edited (except: "thinking aloud" videos or if you need to blur any sensitive information).
Best practices while capturing a screencast
Set up the device and the app or website before starting the recording. For example, if you're going to show a bug that happens after the registration form is filled and you tap on a button to go to the next step, it's best to fill in all information before starting the recording (such as the name, username, email and other fields) to save you some recording time.
Avoid hovering over screen elements for too long with your finger or your mouse. This behaviour can lead you to waste precious recording time. Usually, the viewer will be focused on watching your video so any actions taken or changes to the product will be noticed already.
Remember the time limits (1 minute for Bug Reports screencasts and 15 seconds for Reproductions and User Stories attachments). Since editing your videos is not allowed, instead of trying to fast forward your screencast to make it fit the limits you can check if you didn't record anything that's not actually useful to understand the bug. For the bug reports, normally only one or two extra steps (apart from the last one) are necessary to understand the bug. For Reproductions, you are only required to show the last step to reproduce the bug. Finally, for User Stories, you only need to show the results you've had (which usually means you also need to show only the last step or action taken by you to complete the User Story).
Remember to enable clicks and taps effects. To help the viewer understand which page elements are you interacting with, you are required to show the taps and clicks on your Desktop and Android devices.
Always watch your own screencast after submitting it. Since videos are computer files, they can corrupt when you're converting or uploading them. So opening your own videos and making sure they are good to be reviewed by others will help you to avoid rejections.
If you have the option while recording or converting your video, use preferably the H.264 codec. This is the most widely used codec currently in the world and will guarantee your screencast can be watched on many different devices.