<?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"
	>
<channel>
	<title>Comments on: Test Driven JavaScript using QUnit</title>
	<atom:link href="http://www.eviltester.com/index.php/2008/06/06/test-driven-javascript-using-qunit/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.eviltester.com/index.php/2008/06/06/test-driven-javascript-using-qunit/</link>
	<description>A different view of software testing</description>
	<pubDate>Thu, 09 Sep 2010 04:01:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: KenK</title>
		<link>http://www.eviltester.com/index.php/2008/06/06/test-driven-javascript-using-qunit/#comment-592</link>
		<dc:creator>KenK</dc:creator>
		<pubDate>Sat, 21 Jun 2008 10:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2008/06/08/test-driven-javascript-using-qunit/#comment-592</guid>
		<description>The ‘0 tests of 0 failed’ problem happens because testrunner.js calls runTest() on document ready. Since that script is loaded before your document ready code, the results are generated before your tests are run.

To get rid of the problem, run your tests as a script tag in the head section, which means they run before doc ready.

Thanks for the article, it was a useful intro =)
&lt;em&gt;
Fantastic info thanks.

Comment out...  
// $(document).ready(function(){

and the corresponding closing tags

//});  

And suddenly I have information...

Tests completed in 125 milliseconds.
0 tests of 116 failed.

Excellent - thanks.&lt;/em&gt;


</description>
		<content:encoded><![CDATA[<p>The ‘0 tests of 0 failed’ problem happens because testrunner.js calls runTest() on document ready. Since that script is loaded before your document ready code, the results are generated before your tests are run.</p>
<p>To get rid of the problem, run your tests as a script tag in the head section, which means they run before doc ready.</p>
<p>Thanks for the article, it was a useful intro =)<br />
<em><br />
Fantastic info thanks.</p>
<p>Comment out&#8230;<br />
// $(document).ready(function(){</p>
<p>and the corresponding closing tags</p>
<p>//});  </p>
<p>And suddenly I have information&#8230;</p>
<p>Tests completed in 125 milliseconds.<br />
0 tests of 116 failed.</p>
<p>Excellent - thanks.</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clicking the buttons in QUnit functional testing with JQuery</title>
		<link>http://www.eviltester.com/index.php/2008/06/06/test-driven-javascript-using-qunit/#comment-587</link>
		<dc:creator>Clicking the buttons in QUnit functional testing with JQuery</dc:creator>
		<pubDate>Wed, 18 Jun 2008 21:10:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2008/06/08/test-driven-javascript-using-qunit/#comment-587</guid>
		<description>[...] Test Driven JavaScript using QUnit [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Test Driven JavaScript using QUnit [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jared</title>
		<link>http://www.eviltester.com/index.php/2008/06/06/test-driven-javascript-using-qunit/#comment-581</link>
		<dc:creator>jared</dc:creator>
		<pubDate>Mon, 16 Jun 2008 14:04:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2008/06/08/test-driven-javascript-using-qunit/#comment-581</guid>
		<description>don't feel too bad about the '0 tests of 0 failed' -- after all, the example on jQuery's QUnit page has the same error :)

&lt;em&gt;Thanks Jared. I shall assume that I didn't do something wrong then. :) 

Alan
&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>don&#8217;t feel too bad about the &#8216;0 tests of 0 failed&#8217; &#8212; after all, the example on jQuery&#8217;s QUnit page has the same error :)</p>
<p><em>Thanks Jared. I shall assume that I didn&#8217;t do something wrong then. :) </p>
<p>Alan<br />
</em></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antony Marcano</title>
		<link>http://www.eviltester.com/index.php/2008/06/06/test-driven-javascript-using-qunit/#comment-558</link>
		<dc:creator>Antony Marcano</dc:creator>
		<pubDate>Sat, 07 Jun 2008 09:56:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.eviltester.com/index.php/2008/06/08/test-driven-javascript-using-qunit/#comment-558</guid>
		<description>Nice post Alan,

Thanks for the heads-up on QTest. What would you say are the benefits of QTest over jsUnit?

The QTest uses semantics reminiscent of of a framework I wrote some time ago for some Perl developers who were more used to using Test::More... http://www.testingreflections.com/node/view/5333
(please excuse the formatting issues on that link - trying to fix them)

Love posts like this one... nothing evil about them :-)

Antony Marcano

&lt;em&gt;
Thanks Antony,

I only looked at JSUnit once about a year ago and for some reason I found it hard to get my head around, I don't quite know what I really found difficult, since I just had another look and it seemed simple enough. I do plan to have another look at JSUnit.

Other blogs I read describe JSUnit as slow, and difficult to use for Ajax, but I cannot corroborate that from experience.

JSUnit has not had an update for over 2 years (according to the sourceforge news).

JSUnit being used as part of JQuery testing gives it a whole lot of Qudos.

Some other discussions of &lt;a href="http://www.reddit.com/info/6ix8f/comments/" target="_blank" rel="nofollow"&gt;JSUnit vs Qunit&lt;/a&gt;.

Hope that helps.

Alan
&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Nice post Alan,</p>
<p>Thanks for the heads-up on QTest. What would you say are the benefits of QTest over jsUnit?</p>
<p>The QTest uses semantics reminiscent of of a framework I wrote some time ago for some Perl developers who were more used to using Test::More&#8230; <a href="http://www.testingreflections.com/node/view/5333" rel="nofollow">http://www.testingreflections.com/node/view/5333</a><br />
(please excuse the formatting issues on that link - trying to fix them)</p>
<p>Love posts like this one&#8230; nothing evil about them :-)</p>
<p>Antony Marcano</p>
<p><em><br />
Thanks Antony,</p>
<p>I only looked at JSUnit once about a year ago and for some reason I found it hard to get my head around, I don&#8217;t quite know what I really found difficult, since I just had another look and it seemed simple enough. I do plan to have another look at JSUnit.</p>
<p>Other blogs I read describe JSUnit as slow, and difficult to use for Ajax, but I cannot corroborate that from experience.</p>
<p>JSUnit has not had an update for over 2 years (according to the sourceforge news).</p>
<p>JSUnit being used as part of JQuery testing gives it a whole lot of Qudos.</p>
<p>Some other discussions of <a href="http://www.reddit.com/info/6ix8f/comments/" target="_blank" rel="nofollow">JSUnit vs Qunit</a>.</p>
<p>Hope that helps.</p>
<p>Alan<br />
</em></p>
]]></content:encoded>
	</item>
</channel>
</rss>
