<?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: jsUnit Mock Timeouts and JS Test Driver</title>
	<atom:link href="http://monket.net/blog/2009/07/jsunit-mock-timeouts-and-js-test-driver/feed/" rel="self" type="application/rss+xml" />
	<link>http://monket.net/blog/2009/07/jsunit-mock-timeouts-and-js-test-driver/</link>
	<description></description>
	<lastBuildDate>Mon, 13 Dec 2010 08:11:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Henrik Hjelte</title>
		<link>http://monket.net/blog/2009/07/jsunit-mock-timeouts-and-js-test-driver/comment-page-1/#comment-34</link>
		<dc:creator>Henrik Hjelte</dc:creator>
		<pubDate>Thu, 10 Sep 2009 11:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://monket.net/blog/?p=139#comment-34</guid>
		<description>It Solved my day :-)</description>
		<content:encoded><![CDATA[<p>It Solved my day :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henrik Hjelte</title>
		<link>http://monket.net/blog/2009/07/jsunit-mock-timeouts-and-js-test-driver/comment-page-1/#comment-33</link>
		<dc:creator>Henrik Hjelte</dc:creator>
		<pubDate>Thu, 10 Sep 2009 11:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://monket.net/blog/?p=139#comment-33</guid>
		<description>Thanks for this, it solved my day. I think it is a good solution. If jsTestDriver wants to do anything at all with built-in objects, it should first make local shadowing copies to use. A lot of libraries tweak with built-in objects, and it might be painful to debug all these interactions. The only alternative I see is to let all tests run in an isolated iframe.</description>
		<content:encoded><![CDATA[<p>Thanks for this, it solved my day. I think it is a good solution. If jsTestDriver wants to do anything at all with built-in objects, it should first make local shadowing copies to use. A lot of libraries tweak with built-in objects, and it might be painful to debug all these interactions. The only alternative I see is to let all tests run in an isolated iframe.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

