<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Shawn Wilsher &#187; tests</title>
	<atom:link href="http://shawnwilsher.com/archives/tag/tests/feed" rel="self" type="application/rss+xml" />
	<link>http://shawnwilsher.com</link>
	<description></description>
	<lastBuildDate>Sun, 04 Dec 2011 10:37:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Native Code Tests Now Have an Automagic Profile Directory</title>
		<link>http://shawnwilsher.com/archives/328</link>
		<comments>http://shawnwilsher.com/archives/328#comments</comments>
		<pubDate>Thu, 01 Oct 2009 19:47:55 +0000</pubDate>
		<dc:creator>Shawn Wilsher</dc:creator>
				<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[tests]]></category>

		<guid isPermaLink="false">http://shawnwilsher.com/?p=328</guid>
		<description><![CDATA[Today I checked in bug 517604 which gives native code tests a new, clean profile directory after every run. This puts the native code test harness on par with xpcshell-tests, and tests will no longer have to provide their own profile directory. This means that they no longer have to clean up after themselves. The [...]]]></description>
			<content:encoded><![CDATA[<p>Today I checked in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=517604" title="TestHarness.h should provide a directory provider for a profile directory">bug 517604</a> which gives native code tests a new, clean profile directory after every run.  This puts the native code test harness on par with xpcshell-tests, and tests will no longer have to provide their own profile directory.  This means that they no longer have to clean up after themselves.  The harness will do it for them now!  Happy testing :)</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnwilsher.com/archives/328/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Browser Chrome Tests No Longer Leak</title>
		<link>http://shawnwilsher.com/archives/205</link>
		<comments>http://shawnwilsher.com/archives/205#comments</comments>
		<pubDate>Thu, 22 Jan 2009 00:10:17 +0000</pubDate>
		<dc:creator>Shawn Wilsher</dc:creator>
				<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[leaks]]></category>
		<category><![CDATA[tests]]></category>

		<guid isPermaLink="false">http://shawnwilsher.com/?p=205</guid>
		<description><![CDATA[I just checked in bug 473845 which fixed the last persistent leak in browser chrome tests. It also dropped the leak threshold down to zero for those tests, so leakers will be spotted immediately and properly backed out. Rejoice!]]></description>
			<content:encoded><![CDATA[<p>I just checked in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=473845" title="Break a potential cycle with XPConnect and mozStorageService">bug 473845</a> which fixed the last persistent leak in browser chrome tests.  It also dropped the leak threshold down to zero for those tests, so leakers will be spotted immediately and properly backed out.</p>
<p>Rejoice!</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnwilsher.com/archives/205/feed</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>New way to run tests</title>
		<link>http://shawnwilsher.com/archives/174</link>
		<comments>http://shawnwilsher.com/archives/174#comments</comments>
		<pubDate>Sun, 14 Sep 2008 16:26:36 +0000</pubDate>
		<dc:creator>Shawn Wilsher</dc:creator>
				<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[tests]]></category>

		<guid isPermaLink="false">http://shawnwilsher.com/?p=174</guid>
		<description><![CDATA[Did you know that you no longer have to do some complicated command line incantation to run mochi-style tests? Ted recently landed support for make mochitest-plain, make mochitest-chrome, make mochitest-a11y, and make mochitest-browser-chrome. Today, I just pushed support to specify the --test-path parameter of old. To use it, just add TEST_PATH=your/path/here to the make command [...]]]></description>
			<content:encoded><![CDATA[<p>Did you know that you no longer have to do some complicated command line incantation to run mochi-style tests?  Ted recently landed support for <code>make mochitest-plain</code>, <code>make mochitest-chrome</code>, <code>make mochitest-a11y</code>, and <code>make mochitest-browser-chrome</code>.  Today, I just pushed support to specify the <code>--test-path</code> parameter of old.  To use it, just add <code>TEST_PATH=your/path/here</code> to the make command line.</p>
<p>For those of you who are used to running browser tests, you no longer have to worry about adding in the <code>../browser</code> bits to the path either.  The makefile handles it all for you.  Hurray!</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnwilsher.com/archives/174/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

