<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>Will Norris &#187; osid</title>
	<atom:link href="http://willnorris.com/tag/osid/feed" rel="self" type="application/rss+xml" />
	<link>http://willnorris.com</link>
	<description>there&#039;s more to life than this</description>
	<lastBuildDate>Sun, 05 Feb 2012 17:41:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19719</generator>
<creativeCommons:license>http://creativecommons.org/licenses/by-nc-sa/3.0/</creativeCommons:license>
		<item>
		<title>OKI OSID Unit Testing</title>
		<link>http://willnorris.com/2005/01/oki-osid-unit-testing</link>
		<comments>http://willnorris.com/2005/01/oki-osid-unit-testing#comments</comments>
		<pubDate>Tue, 04 Jan 2005 06:31:37 +0000</pubDate>
		<dc:creator>Will Norris</dc:creator>
				<category><![CDATA[technology]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[osid]]></category>

		<guid isPermaLink="false">http://willnorris.com/wordpress/2005/01/oki-osid-unit-testing</guid>
		<description><![CDATA[As part of hedmaster I&#8217;ve tried to implement as many of the OKI Specs as have made sense. I&#8217;m working on writing extensive JUnit test cases to thoroughly test hedmaster, and I got to thinking about writing a test suite to check for adherence to the OKI Specs. Because the OSID interfaces are designed to [...]]]></description>
			<content:encoded><![CDATA[<p>As part of <a href="http://willnorris.com/projects/hedmaster">hedmaster</a> I&#8217;ve tried to implement as many of the <a href="http://www.okiproject.org/specs">OKI Specs</a>
as have made sense.  I&#8217;m working on writing extensive JUnit test cases to
thoroughly test hedmaster, and I got to thinking about writing a test suite to
check for adherence to the OKI Specs.  Because the OSID interfaces are designed
to enable &#8220;drop in replacement&#8221; of each component, this shouldn&#8217;t be too
difficult.  There would be a test case for each OsidManager that would create
and manipulate objects and simply test that they are instances of the
appropriate OSID.  The user would then write their own test case that passed
their specific implementation of each OsidManger to OsidUnitTest.</p>

<p>As the OSIDs gradually gain acceptance, I think some simple automation like
this would really help people develop proper implementations.</p>
]]></content:encoded>
			<wfw:commentRss>http://willnorris.com/2005/01/oki-osid-unit-testing/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

