<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Web UI Automation and Test using PowerShell</title>
	<atom:link href="http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/</link>
	<description>I'm not that good but I'm not that bad</description>
	<lastBuildDate>Wed, 18 Aug 2010 06:58:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tune Up Your PC &#187; Post Topic &#187; UAC - Accessing Internet Explorer</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-981</link>
		<dc:creator>Tune Up Your PC &#187; Post Topic &#187; UAC - Accessing Internet Explorer</dc:creator>
		<pubDate>Sun, 28 Mar 2010 01:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-981</guid>
		<description>[...] Accessing Internet Explorer can be useful for obtaining Web content. The usual approach uses a COM object called InternetExplorer.Application like this: $ie = New-Object -comObject InternetExplorer.Application$ie.visible = $true$ie.navigate(&#8216;http://www.powershell.com&#8217;)$ie$ie.Document Unfortunately, this approach fails when you use IE with enhanced security (Vista UAC for example). While you can open IE and navigate to the Web page, you will lose access to the document property once the Web site is loaded because the COM object works only for local files. Once you navigate to a Web page, IE launches again with lower privileges, and PowerShell has no way of accessing the new instance. To work around this issue, you can use yet another COM object called Shell.Application. It returns all Explorer windows, including all open IE windows. All you need do is pick the IE window you need, by specifying a keyword found in its title bar. The following example launches a Web page and then waits until a browser window opened with the word &#8220;PowerShell&#8221; in its title bar. Next, the code returns the IE object and accesses the Web page content. &amp; &#8220;$env:programfilesInternet Exploreriexplore.exe&#8221; &#8216;http://powershell.com&#8217;$win = New-Object -comObject Shell.Application$try = 0$ie2 = $nulldo {&#160; Start-Sleep -milliseconds 500&#160; $ie2 = @($win.windows() &#124; ? { $_.locationName -like &#8216;*PowerShell*&#8217; })[0]&#160; $try ++&#160; if ($try -gt 20) {&#160;&#160;&#160; Throw &#8220;Web Page cannot be opened.&#8221;&#160; }} while ($ie2 -eq $null)$ie2.document$ie2.Document.body.innerHTML http://powershell.com/cs/blogs/tips/archive/2009/04/03/accessing-internet-explorer.aspx&#160; &#160;http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Accessing Internet Explorer can be useful for obtaining Web content. The usual approach uses a COM object called InternetExplorer.Application like this: $ie = New-Object -comObject InternetExplorer.Application$ie.visible = $true$ie.navigate(&#8216;http://www.powershell.com&#8217;)$ie$ie.Document Unfortunately, this approach fails when you use IE with enhanced security (Vista UAC for example). While you can open IE and navigate to the Web page, you will lose access to the document property once the Web site is loaded because the COM object works only for local files. Once you navigate to a Web page, IE launches again with lower privileges, and PowerShell has no way of accessing the new instance. To work around this issue, you can use yet another COM object called Shell.Application. It returns all Explorer windows, including all open IE windows. All you need do is pick the IE window you need, by specifying a keyword found in its title bar. The following example launches a Web page and then waits until a browser window opened with the word &#8220;PowerShell&#8221; in its title bar. Next, the code returns the IE object and accesses the Web page content. &amp; &#8220;$env:programfilesInternet Exploreriexplore.exe&#8221; &#8216;http://powershell.com&#8217;$win = New-Object -comObject Shell.Application$try = 0$ie2 = $nulldo {&nbsp; Start-Sleep -milliseconds 500&nbsp; $ie2 = @($win.windows() | ? { $_.locationName -like &#8216;*PowerShell*&#8217; })[0]&nbsp; $try ++&nbsp; if ($try -gt 20) {&nbsp;&nbsp;&nbsp; Throw &#8220;Web Page cannot be opened.&#8221;&nbsp; }} while ($ie2 -eq $null)$ie2.document$ie2.Document.body.innerHTML <a href="http://powershell.com/cs/blogs/tips/archive/2009/04/03/accessing-internet-explorer.aspx&#038;nbsp" rel="nofollow">http://powershell.com/cs/blogs/tips/archive/2009/04/03/accessing-internet-explorer.aspx&#038;nbsp</a>; &nbsp;http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Davo</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-979</link>
		<dc:creator>Davo</dc:creator>
		<pubDate>Fri, 19 Mar 2010 04:18:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-979</guid>
		<description>Philippe..you ROCK! This is an excellent post, I will find this very useful. Thanks very much.</description>
		<content:encoded><![CDATA[<p>Philippe..you ROCK! This is an excellent post, I will find this very useful. Thanks very much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-978</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Tue, 02 Mar 2010 20:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-978</guid>
		<description>I also use that stuff for webtesting... 
As i didn&#039;t find a way to automate a fileupload natively i did this with waitn in posh.(http://watin.sourceforge.net/)
Pretty sure you ca n handle PopUps as well</description>
		<content:encoded><![CDATA[<p>I also use that stuff for webtesting&#8230;<br />
As i didn&#8217;t find a way to automate a fileupload natively i did this with waitn in posh.(http://watin.sourceforge.net/)<br />
Pretty sure you ca n handle PopUps as well</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chan</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-974</link>
		<dc:creator>chan</dc:creator>
		<pubDate>Thu, 21 Jan 2010 07:58:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-974</guid>
		<description>hi do you have any idea, how to detect popup window using powershell?</description>
		<content:encoded><![CDATA[<p>hi do you have any idea, how to detect popup window using powershell?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carl</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-390</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Wed, 29 Jul 2009 10:59:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-390</guid>
		<description>Great stuff, thanks very much for posting this..</description>
		<content:encoded><![CDATA[<p>Great stuff, thanks very much for posting this..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philippe</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-386</link>
		<dc:creator>Philippe</dc:creator>
		<pubDate>Thu, 16 Jul 2009 21:32:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-386</guid>
		<description>Nope, didn&#039;t know about that tool. Looks very intresting. Thanks for pointing it out!

However, what I wrote is more for a personnal use. The application I&#039;m currently working on need a few forms of inputs before reaching the part that I&#039;m working on, so this comes in handy.</description>
		<content:encoded><![CDATA[<p>Nope, didn&#8217;t know about that tool. Looks very intresting. Thanks for pointing it out!</p>
<p>However, what I wrote is more for a personnal use. The application I&#8217;m currently working on need a few forms of inputs before reaching the part that I&#8217;m working on, so this comes in handy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Ukleja</title>
		<link>http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/comment-page-1/#comment-383</link>
		<dc:creator>Jack Ukleja</dc:creator>
		<pubDate>Wed, 15 Jul 2009 02:00:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.pvle.be/2009/06/web-ui-automationtest-using-powershell/#comment-383</guid>
		<description>Have you tried using Selenium RC? A very easy to use plug-in for Firefox that lets you record and playback and make assertions. &quot;No code required&quot;.</description>
		<content:encoded><![CDATA[<p>Have you tried using Selenium RC? A very easy to use plug-in for Firefox that lets you record and playback and make assertions. &#8220;No code required&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
