Leverage audio and video recording tools for bug reporting
In the past, we've shared a couple of tools for capturing desktop audio and video. In this post, we wanted to reinforce the idea of using audio and video recording tools for bug reporting. Instead of just submitting the steps to reproduce and a couple screenshots, try including a verbal description and show the bug or issue in action if that's possible. This often removes any ambiguity, and it can sometimes provide details to the development team that you may not have thought to mention (like the browser being used, or the screen resolution, etc).
This tip was part of a brainstorm developed at the September 2011 Indianapolis Workshop on Software Testing on the topic of "Documenting for Testing." The attendees of that workshop (and participants in the brainstorm) included: Charlie Audritsh, Scott Barber, Rick Grey, Michael Kelly, Natalie Mego, Charles Penn, Margie Weaver, and Tina Zaza.
October 10th, 2011 - 15:01
I’d personally find it tedious to sit through a video or audio, rather than a well-written bug report. I do agree though, that on a select few occasions, audio and/or video may be the best way to convey additional information.
I’d caution against using ONLY video or audio, though.
Some of the same reasons that pictures make for insufficient bug reports apply to video/audio as well (particularly the warning about searching):
http://strazzere.blogspot.com/2010/04/picture-is-not-worth-thousand-words.html
October 11th, 2011 - 02:59
I would agree on what Joe has mentioned about ONLY clause in the second paragraph of his comment.
Audio and Video style of bug reporting helps in some of the cases, I have used it in my bug reporting in the past and even now in some cases based on the bug.
Reference: You could download CamStudio which is a freeware. Got good features with reference to being free.
– Santhosh Tuppad