Sara Ford - Analyzing a Test Case Failure (Maddog Part 3)
- Posted: Feb 04, 2005 at 1:18 PM
- 74,898 Views
- 2 Comments
Now that the test case owner knows why the test case has failed, the information, usually in the form of a bug id, is entered into Maddog. This tracking allows everyone, not just the test case owners, to know how many product bugs are affecting the current
build.
In this clip, watch MHagman and SaraF analyze a test case failure in Maddog.
For more Devdiv updates check out our C9 site: http://channel9.msdn.com/devdiv
- josh
In this clip, watch MHagman and SaraF analyze a test case failure in Maddog.
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.
More posts in this blog
-
Kevin Schofield - Tour of Microsoft Research, Part…
-
Sara Ford - Analyzing a Test Case Failure (Maddog…
-
Kevin Schofield - Tour of Microsoft Research, Part…
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
To create the automated tests, do you record and then playback mouse and keyboard events? I was assuming you'd do it programmatically with COM or maybe send WM_COMMANDs.
A while ago I had to automate the AOL dial-up window because it didn't use a standard RAS entry. Instead I found the control IDs with Spy++ and used PostMessage and SendMessage to click the right buttons. I guess you don't do it that way because your goal is to simulate an actual user?
Record and playback is definitely one way to automate tests. Our primary method is to use a combination of MSAA and Win32 api calls, like sending messages to a control as you describe above. We drive the UI (meaning we use the mouse and/or keyboard to click on menus, buttons, etc) as much as possible to simulate an actual user, and it does a really good job.
Brian McMaster, one of our software testing architects (someone who designs our automation framework) wrote this whitepaper on Automating WinForms...
http://msdn.microsoft.com/library/en-us/dnwinforms/html/autowforms.asp
Hope this helps!
-sara
Remove this comment
Remove this thread
close