<?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: Automated Unit Testing for JavaScript</title>
	<atom:link href="http://aptoma.com/select.star/2010/03/03/automated-unit-testing-for-javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://aptoma.com/select.star/2010/03/03/automated-unit-testing-for-javascript/</link>
	<description>web-development, and other issues we really, really care about</description>
	<lastBuildDate>Mon, 29 Aug 2011 14:56:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Bowmanave</title>
		<link>http://aptoma.com/select.star/2010/03/03/automated-unit-testing-for-javascript/comment-page-1/#comment-8097</link>
		<dc:creator>Bowmanave</dc:creator>
		<pubDate>Thu, 20 Jan 2011 05:31:22 +0000</pubDate>
		<guid isPermaLink="false">http://aptoma.com/select.star/?p=1192#comment-8097</guid>
		<description>It would probably be good to start a javascript testing project in contrib (e.g. qunit), before trying to move it into core for Drupal 8. That way, we can have tests for Drupal 7 even if they&#039;re not in core, and it would be a great starting point for a JavaScript testing framework for Drupal 8. 
 
Also, I&#039;d like to note that I no longer think that using qunit is the best approach. While qunit is a wonderful automated JavaScript testing framework, my understanding is that it&#039;s really designed to test JavaScript independent of web content, not JavaScript that depends on PHP-driven web content (such as collapsible fieldsets, sticky table headers, tabledrag, and nearly every other major JavaScript implementation in Drupal). I think we should work out the details of a testing framework in contrib before coming in with a core patch. </description>
		<content:encoded><![CDATA[<p>It would probably be good to start a javascript testing project in contrib (e.g. qunit), before trying to move it into core for Drupal 8. That way, we can have tests for Drupal 7 even if they&#39;re not in core, and it would be a great starting point for a JavaScript testing framework for Drupal 8. </p>
<p>Also, I&#39;d like to note that I no longer think that using qunit is the best approach. While qunit is a wonderful automated JavaScript testing framework, my understanding is that it&#39;s really designed to test JavaScript independent of web content, not JavaScript that depends on PHP-driven web content (such as collapsible fieldsets, sticky table headers, tabledrag, and nearly every other major JavaScript implementation in Drupal). I think we should work out the details of a testing framework in contrib before coming in with a core patch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pahen</title>
		<link>http://aptoma.com/select.star/2010/03/03/automated-unit-testing-for-javascript/comment-page-1/#comment-8044</link>
		<dc:creator>pahen</dc:creator>
		<pubDate>Thu, 04 Mar 2010 07:27:33 +0000</pubDate>
		<guid isPermaLink="false">http://aptoma.com/select.star/?p=1192#comment-8044</guid>
		<description>Thanks for the tip but in fact we&#039;re using TestCase without using Ruby. But if we starting use Ruby, I&#039;ll definitely take a look at it. </description>
		<content:encoded><![CDATA[<p>Thanks for the tip but in fact we&#039;re using TestCase without using Ruby. But if we starting use Ruby, I&#039;ll definitely take a look at it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Parkes</title>
		<link>http://aptoma.com/select.star/2010/03/03/automated-unit-testing-for-javascript/comment-page-1/#comment-8043</link>
		<dc:creator>Steven Parkes</dc:creator>
		<pubDate>Wed, 03 Mar 2010 16:47:33 +0000</pubDate>
		<guid isPermaLink="false">http://aptoma.com/select.star/?p=1192#comment-8043</guid>
		<description>Since you use Ruby, you might also want to look at the Ruby/Spidermonkey fork of env.js at &lt;a href=&quot;http://github.com/smparkes/env-js.&quot; rel=&quot;nofollow&quot;&gt;http://github.com/smparkes/env-js.&lt;/a&gt; </description>
		<content:encoded><![CDATA[<p>Since you use Ruby, you might also want to look at the Ruby/Spidermonkey fork of env.js at <a href="http://github.com/smparkes/env-js." rel="nofollow">http://github.com/smparkes/env-js.</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

