<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Comment Feed for Channel 9 - Sara Ford - Analyzing a Test Case Failure (Maddog Part 3)</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Blogs/TheChannel9Team/Sara-Ford-Analyzing-a-Test-Case-Failure-Maddog-Part-3/RSS"></atom:link>
	<image>
		<url>http://ecn.channel9.msdn.com/o9/previewImages/100/38352_100x75.jpg</url>
		<title>Channel 9 - Sara Ford - Analyzing a Test Case Failure (Maddog Part 3)</title>
		<link></link>
	</image>
	<description>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.&amp;nbsp; 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</description>
	<link></link>
	<language>en</language>
	<pubDate>Wed, 22 May 2013 10:19:46 GMT</pubDate>
	<lastBuildDate>Wed, 22 May 2013 10:19:46 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<item>
		<title>Re: Sara Ford - Analyzing a Test Case Failure (Maddog Part 3)</title>
		<description>
			<![CDATA[
<p>To create the automated tests, do you record and then playback mouse and keyboard events?&nbsp; I was assuming you'd do it programmatically with&nbsp;COM or maybe send WM_COMMANDs.</p>
<p>A while ago I had to automate the AOL dial-up window because it didn't use a standard RAS entry.&nbsp; Instead I found the control IDs with Spy&#43;&#43; and used PostMessage and SendMessage to click the right buttons.&nbsp; I guess you don't do it that way because your goal
 is to simulate an actual user?</p>
<p>posted by BinaryBoy</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/TheChannel9Team/Sara-Ford-Analyzing-a-Test-Case-Failure-Maddog-Part-3#c632432375910000000</link>
		<pubDate>Sat, 05 Feb 2005 21:59:51 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/TheChannel9Team/Sara-Ford-Analyzing-a-Test-Case-Failure-Maddog-Part-3#c632432375910000000</guid>
		<dc:creator>BinaryBoy</dc:creator>
	</item>
	<item>
		<title>Re: Sara Ford - Analyzing a Test Case Failure (Maddog Part 3)</title>
		<description>
			<![CDATA[
<p>Record and playback is definitely one way to automate tests.&nbsp; Our primary method is to use a combination of MSAA and Win32 api calls, like sending messages to a control as you describe above.&nbsp; We drive the UI (meaning we use the mouse and/or keyboard&nbsp;to
 click on menus, buttons, etc)&nbsp;as much as possible to simulate an actual user, and it does a really good job.<br>
<br>
Brian McMaster, one of our software testing architects (someone who designs&nbsp;our automation framework) wrote this whitepaper on Automating WinForms...<br>
<a href="http://msdn.microsoft.com/library/en-us/dnwinforms/html/autowforms.asp">http://msdn.microsoft.com/library/en-us/dnwinforms/html/autowforms.asp</a><br>
<br>
Hope this helps!<br>
-sara<br>
</p>
<p>posted by saraford</p>]]>
		</description>
		<link>http://channel9.msdn.com/Blogs/TheChannel9Team/Sara-Ford-Analyzing-a-Test-Case-Failure-Maddog-Part-3#c632434818270000000</link>
		<pubDate>Tue, 08 Feb 2005 17:50:27 GMT</pubDate>
		<guid isPermaLink="true">http://channel9.msdn.com/Blogs/TheChannel9Team/Sara-Ford-Analyzing-a-Test-Case-Failure-Maddog-Part-3#c632434818270000000</guid>
		<dc:creator>saraford</dc:creator>
	</item>
</channel>
</rss>