Sara Ford - Finding and Logging a Bug (Maddog Part 4)
- Posted: Feb 07, 2005 at 2:15 PM
- 78,642 Views
- 4 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Logging bugs is easy. Logging “QA” quality bugs takes a little more time, energy, and focus. Logging a bug requires a well-written title and the fewest number of steps to reproduce the bug.
In this clip, SaraF “raids” a product bug found while investigating a test case failure, demo’ing how to minimize the number of repro steps and how to write an effective bug title.
For more information on writing a good bug report check out this post from the Product Feedback Center blog.
For more Devdiv updates check out our C9 site: http://channel9.msdn.com/devdiv
- josh
In this clip, SaraF “raids” a product bug found while investigating a test case failure, demo’ing how to minimize the number of repro steps and how to write an effective bug title.
For more information on writing a good bug report check out this post from the Product Feedback Center blog.
For more Devdiv updates check out our C9 site: http://channel9.msdn.com/devdiv
- josh
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Also, i don't think the programmer is the guilty party here, if there even is a guilty party. The triage team said that this was how the data tip was designed, and from their usability studies, no one had run into this issue before. I think that's what makes me a good tester - i don't interact with UI the same way most people do. So, I can find these scenarios and get triage teams to make the right call, before the users run into them.
Thanks!
-sara
I usually like my tests to all pass. If you get a bug that is postponed do you just live with a failing test, do you remove the scenario for now, or do you "reverse" test it (test for the wrong results until they fix it)? Is this the first time that this test was run?
Mark
This test has been running for as long as we've had an editor =)
Thanks!
-sara
Remove this comment
Remove this thread
close