<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>NUnitLite Wiki &amp; Documentation Rss Feed</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=Home</link><description>NUnitLite Wiki Rss Description</description><item><title>Updated Wiki: Home</title><link>http://nunitlite.codeplex.com/Wiki/View.aspx?title=Home&amp;version=15</link><description>&lt;div class="wikidoc"&gt;&lt;b&gt;Important Notice&lt;/b&gt;&lt;br /&gt;NUnitLite development as been discontinued on Codeplex. You can still download the code through release 0.20. &lt;br /&gt;&lt;br /&gt;The latest code is hosted on http://launchpad.net/nunitlite and further releases will be from that site.&lt;br /&gt;&lt;br /&gt;For discussions of NUnitLite, please join the nunitlite group on Google.&lt;br /&gt;&lt;br /&gt;You can still view our &lt;a href="http://nunitlite.codeplex.com/Wiki/View.aspx?title=OldHomePage"&gt;OldHomePage&lt;/a&gt;&lt;/div&gt;</description><author>cpoole</author><pubDate>Sun, 14 Jun 2009 18:29:54 GMT</pubDate><guid isPermaLink="false">Updated Wiki: Home 20090614062954P</guid></item><item><title>Updated Wiki: Home</title><link>http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=Home&amp;version=14</link><description>&lt;div class="wikidoc"&gt;
&lt;b&gt;Important Notice&lt;/b&gt;&lt;br /&gt;NUnitLite development as been discontinued on Codeplex. The latest code is hosted on http://launchpad.net/nunitlite and further releases will be from that site.&lt;br /&gt; &lt;br /&gt;You can still view our &lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=OldHomePage&amp;amp;referringTitle=Home"&gt;OldHomePage&lt;/a&gt;&lt;br /&gt;
&lt;/div&gt;</description><author>cpoole</author><pubDate>Sun, 21 Dec 2008 00:03:51 GMT</pubDate><guid isPermaLink="false">Updated Wiki: Home 20081221120351A</guid></item><item><title>Updated Wiki: OldHomePage</title><link>http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=OldHomePage&amp;version=2</link><description>&lt;div class="wikidoc"&gt;
&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=News%20Feeds&amp;amp;referringTitle=OldHomePage"&gt;News Feeds&lt;/a&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Welcome to the NUnitLite Project&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;NUnitLite&lt;/b&gt; is a a lightweight test framework for .Net, based on a subset of NUnit's features. It will use minimal resources and will run under .Net 1.0, 1.1 and 2.0, Mono 1.0 and 2.0 profiles and the versions 1 and 2 of the compact framework. &lt;br /&gt; &lt;br /&gt;NUnitLite is an Open Source project, available under the Open Source License (&amp;quot;OSL&amp;quot;) 3.0.&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Why an NUnitLite?&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;Since it's introduction, &lt;b&gt;NUnit&lt;/b&gt; has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes.&lt;br /&gt; &lt;br /&gt;Basically, we want &lt;b&gt;NUnitLite&lt;/b&gt; to be a very simple &lt;b&gt;NUnit&lt;/b&gt;, one that could be included as source right with the tests themselves. It should implement a subset of the features of full &lt;b&gt;NUnit&lt;/b&gt;. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of &lt;b&gt;NUnit&lt;/b&gt; itself.&lt;br /&gt; &lt;br /&gt;The name &lt;b&gt;NUnitLite&lt;/b&gt; is, of course, inspired by Mike Feathers' &lt;b&gt;CppUnitLite&lt;/b&gt;.&lt;br /&gt; &lt;br /&gt;For further information, see&lt;br /&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Vision&amp;amp;referringTitle=OldHomePage"&gt;NUnitLite Vision&lt;/a&gt; - our high-level vision of what we want to build&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Features&amp;amp;referringTitle=OldHomePage"&gt;NUnitLite Features&lt;/a&gt; - our list of features for NUnitLite&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>cpoole</author><pubDate>Sun, 21 Dec 2008 00:01:44 GMT</pubDate><guid isPermaLink="false">Updated Wiki: OldHomePage 20081221120144A</guid></item><item><title>Updated Wiki: OldHomePage</title><link>http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=OldHomePage&amp;version=1</link><description>&lt;div class="wikidoc"&gt;
&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=News%20Feeds&amp;amp;referringTitle=OldHomePage"&gt;News Feeds&lt;/a&gt;&lt;br /&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=OldHomePage&amp;amp;referringTitle=OldHomePage"&gt;OldHomePage&lt;/a&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Welcome to the NUnitLite Project&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;NUnitLite&lt;/b&gt; is a a lightweight test framework for .Net, based on a subset of NUnit's features. It will use minimal resources and will run under .Net 1.0, 1.1 and 2.0, Mono 1.0 and 2.0 profiles and the versions 1 and 2 of the compact framework. &lt;br /&gt; &lt;br /&gt;NUnitLite is an Open Source project, available under the Open Source License (&amp;quot;OSL&amp;quot;) 3.0.&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Why an NUnitLite?&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;Since it's introduction, &lt;b&gt;NUnit&lt;/b&gt; has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes.&lt;br /&gt; &lt;br /&gt;Basically, we want &lt;b&gt;NUnitLite&lt;/b&gt; to be a very simple &lt;b&gt;NUnit&lt;/b&gt;, one that could be included as source right with the tests themselves. It should implement a subset of the features of full &lt;b&gt;NUnit&lt;/b&gt;. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of &lt;b&gt;NUnit&lt;/b&gt; itself.&lt;br /&gt; &lt;br /&gt;The name &lt;b&gt;NUnitLite&lt;/b&gt; is, of course, inspired by Mike Feathers' &lt;b&gt;CppUnitLite&lt;/b&gt;.&lt;br /&gt; &lt;br /&gt;For further information, see&lt;br /&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Vision&amp;amp;referringTitle=OldHomePage"&gt;NUnitLite Vision&lt;/a&gt; - our high-level vision of what we want to build&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Features&amp;amp;referringTitle=OldHomePage"&gt;NUnitLite Features&lt;/a&gt; - our list of features for NUnitLite&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>cpoole</author><pubDate>Sun, 21 Dec 2008 00:00:59 GMT</pubDate><guid isPermaLink="false">Updated Wiki: OldHomePage 20081221120059A</guid></item><item><title>Updated Wiki: Home</title><link>http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=Home&amp;version=13</link><description>&lt;div class="wikidoc"&gt;
&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=News%20Feeds&amp;amp;referringTitle=Home"&gt;News Feeds&lt;/a&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Important Notice&lt;/b&gt;&lt;br /&gt;NUnitLite development as been discontinued on Codeplex. The latest code is hosted on http://launchpad.net/nunitlite&lt;br /&gt; &lt;br /&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=OldHomePage&amp;amp;referringTitle=Home"&gt;OldHomePage&lt;/a&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Welcome to the NUnitLite Project&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;NUnitLite&lt;/b&gt; is a a lightweight test framework for .Net, based on a subset of NUnit's features. It will use minimal resources and will run under .Net 1.0, 1.1 and 2.0, Mono 1.0 and 2.0 profiles and the versions 1 and 2 of the compact framework. &lt;br /&gt; &lt;br /&gt;NUnitLite is an Open Source project, available under the Open Source License (&amp;quot;OSL&amp;quot;) 3.0.&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Why an NUnitLite?&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;Since it's introduction, &lt;b&gt;NUnit&lt;/b&gt; has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes.&lt;br /&gt; &lt;br /&gt;Basically, we want &lt;b&gt;NUnitLite&lt;/b&gt; to be a very simple &lt;b&gt;NUnit&lt;/b&gt;, one that could be included as source right with the tests themselves. It should implement a subset of the features of full &lt;b&gt;NUnit&lt;/b&gt;. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of &lt;b&gt;NUnit&lt;/b&gt; itself.&lt;br /&gt; &lt;br /&gt;The name &lt;b&gt;NUnitLite&lt;/b&gt; is, of course, inspired by Mike Feathers' &lt;b&gt;CppUnitLite&lt;/b&gt;.&lt;br /&gt; &lt;br /&gt;For further information, see&lt;br /&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Vision&amp;amp;referringTitle=Home"&gt;NUnitLite Vision&lt;/a&gt; - our high-level vision of what we want to build&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Features&amp;amp;referringTitle=Home"&gt;NUnitLite Features&lt;/a&gt; - our list of features for NUnitLite&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>cpoole</author><pubDate>Sun, 21 Dec 2008 00:00:27 GMT</pubDate><guid isPermaLink="false">Updated Wiki: Home 20081221120027A</guid></item><item><title>Updated Wiki: Home</title><link>http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=Home&amp;version=12</link><description>&lt;div class="wikidoc"&gt;
&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=News%20Feeds&amp;amp;referringTitle=Home"&gt;News Feeds&lt;/a&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Important Notice&lt;/b&gt;&lt;br /&gt;NUnitLite development as been discontinued on Codeplex. The latest code is hosted on http://launchpad.net/nunitlite&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Welcome to the NUnitLite Project&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;NUnitLite&lt;/b&gt; is a a lightweight test framework for .Net, based on a subset of NUnit's features. It will use minimal resources and will run under .Net 1.0, 1.1 and 2.0, Mono 1.0 and 2.0 profiles and the versions 1 and 2 of the compact framework. &lt;br /&gt; &lt;br /&gt;NUnitLite is an Open Source project, available under the Open Source License (&amp;quot;OSL&amp;quot;) 3.0.&lt;br /&gt; &lt;br /&gt;&lt;b&gt;Why an NUnitLite?&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;Since it's introduction, &lt;b&gt;NUnit&lt;/b&gt; has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes.&lt;br /&gt; &lt;br /&gt;Basically, we want &lt;b&gt;NUnitLite&lt;/b&gt; to be a very simple &lt;b&gt;NUnit&lt;/b&gt;, one that could be included as source right with the tests themselves. It should implement a subset of the features of full &lt;b&gt;NUnit&lt;/b&gt;. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of &lt;b&gt;NUnit&lt;/b&gt; itself.&lt;br /&gt; &lt;br /&gt;The name &lt;b&gt;NUnitLite&lt;/b&gt; is, of course, inspired by Mike Feathers' &lt;b&gt;CppUnitLite&lt;/b&gt;.&lt;br /&gt; &lt;br /&gt;For further information, see&lt;br /&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Vision&amp;amp;referringTitle=Home"&gt;NUnitLite Vision&lt;/a&gt; - our high-level vision of what we want to build&lt;/li&gt;&lt;li&gt;&lt;a href="http://www.codeplex.com/NUnitLite/Wiki/View.aspx?title=NUnitLite%20Features&amp;amp;referringTitle=Home"&gt;NUnitLite Features&lt;/a&gt; - our list of features for NUnitLite&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;</description><author>cpoole</author><pubDate>Sat, 20 Dec 2008 23:56:52 GMT</pubDate><guid isPermaLink="false">Updated Wiki: Home 20081220115652P</guid></item><item><title>UPDATED WIKI: NUnitLite Features</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Features&amp;version=14</link><description>&lt;p&gt;
&lt;h3&gt;NUnitLite Features&lt;/h3&gt;
&lt;/p&gt;
&lt;p&gt;
The following features are available in the current release&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestCases&lt;/b&gt;&lt;br/&gt;
Test fixtures may be created by inheriting from the TestCase class. Any methods begining with the case-insensitive prefix "test" are identified as tests. SetUp and TearDown may be overridden and will be called before and after each test.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestFixtures&lt;/b&gt;&lt;br/&gt;
A non-TestCase class may be used as a fixture by marking it with the TestFixtureAttribute. Within such a class, test methods are marked by the TestAttribute, setup by the SetUpAttribute and teardown by the TearDownAttribute. The ExpectedExceptionAttribute is also supported on test methods.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Note:&lt;/b&gt; TestFixtureAttribute, TestAttribute and ExpectedExceptionAttribute may also be used on TestCase-derived classes. SetUpAttribute and TearDownAttribute are ignored on such classes.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestSuites&lt;/b&gt;&lt;br/&gt;
By use of the static Suite property, arbitrary suites of tests may be manually created. A suite may consist of individual test cases, entire test fixtures or other suites.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Asserts&lt;/b&gt;&lt;br/&gt;
The programmer expresses expected test conditions using the Assert class. The existing functionality of most current NUnit Assert methods is supported, but the syntax has been changed to use a more extensible format.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Running Tests&lt;/b&gt;&lt;br/&gt;
Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests. Tests are executed in the order found, without any guarantees of ordering. A separate instance of the fixture object is created for each test case executed by NUnitLite.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Console Runner&lt;/b&gt;&lt;br/&gt;
The embedded console runner produces a summary of tests run and lists any errors or failures.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Deployment&lt;/b&gt;&lt;br/&gt;
The current release is only suitable for embedded use. Tests are created in an exe project and the NUnitLite files may be included in the same project or compiled separately. In the case of separate compilation, the test project must include a small stub that starts NUnitLite execution.&lt;br/&gt;
&lt;br/&gt;
&lt;/p&gt;
</description><author>cpoole</author><pubDate>Tue, 29 Aug 2006 21:24:40 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Features 20060829092440P</guid></item><item><title>UPDATED WIKI: NUnitLite Features</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Features&amp;version=13</link><description>&lt;p&gt;
&lt;h3&gt;NUnitLite Features&lt;/h3&gt;
&lt;/p&gt;
&lt;p&gt;
The following features are available in the current release&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestCases&lt;/b&gt;&lt;br/&gt;
Test fixtures may be created by inheriting from the TestCase class. Any methods begining with the case-insensitive prefix "test" are identified as tests. SetUp and TearDown may be overridden and will be called before and after each test.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestFixtures&lt;/b&gt;&lt;br/&gt;
A non-TestCase class may be used as a fixture by marking it with the TestFixtureAttribute. Within such a class, test methods are marked by the TestAttribute, setup by the SetUpAttribute and teardown by the TearDownAttribute. The ExpectedExceptionAttribute is also supported on test methods.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Note:&lt;/b&gt; TestFixtureAttribute, TestAttribute and ExpectedExceptionAttribute may also be used on TestCase-derived classes. SetUpAttribute and TearDownAttribute are ignored on such classes.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Asserts&lt;/b&gt;&lt;br/&gt;
The programmer expresses expected test conditions using the Assert class. The existing functionality of most current NUnit Assert methods is supported, but the syntax has been changed to use a more extensible format.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Running Tests&lt;/b&gt;&lt;br/&gt;
Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests. Tests are executed in the order found, without any guarantees of ordering. A separate instance of the fixture object is created for each test case executed by NUnitLite.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Console Runner&lt;/b&gt;&lt;br/&gt;
The embedded console runner produces a summary of tests run and lists any errors or failures.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Deployment&lt;/b&gt;&lt;br/&gt;
The current release is only suitable for embedded use. Tests are created in an exe project and the NUnitLite files may be included in the same project or compiled separately. In the case of separate compilation, the test project must include a small stub that starts NUnitLite execution.&lt;br/&gt;
&lt;br/&gt;
&lt;/p&gt;
</description><author>cpoole</author><pubDate>Tue, 29 Aug 2006 21:22:59 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Features 20060829092259P</guid></item><item><title>UPDATED WIKI: NUnitLite Features</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Features&amp;version=12</link><description>&lt;p&gt;
&lt;h3&gt;NUnitLite Features&lt;/h3&gt;
&lt;/p&gt;
&lt;p&gt;
The following features are available in the current release&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestCases&lt;/b&gt;&lt;br/&gt;
Test fixtures may be created by inheriting from the TestCase class. Any methods begining with the case-insensitive prefix "test" are identified as tests. SetUp and TearDown may be overridden and will be called before and after each test.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;TestFixtures&lt;/b&gt;&lt;br/&gt;
A non-TestCase class may be used as a fixture by marking it with the &lt;b&gt;TestFixtureAttribute&lt;/b&gt;. Within such a class, test methods are marked by the &lt;b&gt;TestAttribute&lt;/b&gt;, setup by the &lt;b&gt;SetUpAttribute&lt;/b&gt; and teardown by the &lt;b&gt;TearDownAttribute&lt;/b&gt;. The &lt;b&gt;ExpectedExceptionAttribute&lt;/b&gt; is also supported on test methods.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Note:&lt;/b&gt; TestFixtureAttribute, TestAttribute and ExpectedExceptionAttribute may also be used on TestCase-derived classes. SetUpAttribute and TearDownAttribute are ignored on such classes.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Asserts&lt;/b&gt;&lt;br/&gt;
The programmer expresses expected test conditions using the Assert class. The existing functionality of most current NUnit Assert methods is supported, but the syntax has been changed to use a more extensible format.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Running Tests&lt;/b&gt;&lt;br/&gt;
Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests. Tests are executed in the order found, without any guarantees of ordering. A separate instance of the fixture object is created for each test case executed by NUnitLite.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Console Runner&lt;/b&gt;&lt;br/&gt;
The embedded console runner produces a summary of tests run and lists any errors or failures.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Deployment&lt;/b&gt;&lt;br/&gt;
The current release is only suitable for embedded use. Tests are created in an exe project and the NUnitLite files may be included in the same project or compiled separately. In the case of separate compilation, the test project must include a small stub that starts NUnitLite execution.&lt;br/&gt;
&lt;br/&gt;
&lt;/p&gt;
</description><author>cpoole</author><pubDate>Tue, 29 Aug 2006 21:22:06 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Features 20060829092206P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=Home&amp;version=10</link><description>&lt;p&gt;
&lt;b&gt;Welcome to the NUnitLite Project&lt;/b&gt;&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;NUnitLite&lt;/b&gt; is a a lightweight test framework for .Net, based on a subset of NUnit's features. It will use minimal resources and will run under .Net 1.0, 1.1 and 2.0, Mono 1.0 and 2.0 profiles and the versions 1 and 2 of the compact framework. &lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
NUnitLite is an Open Source project, available under the Open Source License ("OSL") 3.0.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;b&gt;Why an NUnitLite?&lt;/b&gt;&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
Since it's introduction, &lt;b&gt;NUnit&lt;/b&gt; has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
Basically, we want &lt;b&gt;NUnitLite&lt;/b&gt; to be a very simple &lt;b&gt;NUnit&lt;/b&gt;, one that could be included as source right with the tests themselves. It should implement a subset of the features of full &lt;b&gt;NUnit&lt;/b&gt;. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of &lt;b&gt;NUnit&lt;/b&gt; itself.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
The name &lt;b&gt;NUnitLite&lt;/b&gt; is, of course, inspired by Mike Feathers' &lt;b&gt;CppUnitLite&lt;/b&gt;.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
For further information, see&lt;br/&gt;
&lt;ul&gt;&lt;li&gt;&lt;a href="http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;amp;title=NUnitLite%20Vision"&gt;NUnitLite Vision&lt;/a&gt; - our high-level vision of what we want to build&lt;/li&gt;
&lt;li&gt;&lt;a href="http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;amp;title=NUnitLite%20Features"&gt;NUnitLite Features&lt;/a&gt; - our list of features for NUnitLite&lt;/li&gt;
&lt;/ul&gt;&lt;br/&gt;
&lt;/p&gt;
</description><author>cpoole</author><pubDate>Tue, 29 Aug 2006 20:55:20 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20060829085520P</guid></item><item><title>UPDATED WIKI: NUnitLite Vision</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Vision&amp;version=16</link><description>&lt;p&gt;
&lt;h3&gt;The NUnitLite Vision&lt;/h3&gt;
&lt;/p&gt;
&lt;p&gt;
NUnitLite is a lightweight test framework for .Net, implementing a limited subset of NUnit's features. It will use minimal resources and be suitable for execution on various classes of devices.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
NUnit itself is fairly full-featured and becomes more so with each release. As a result, it is difficult to use in certain projects, such as embedded applications and testing add-ins for other software products.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
NUnitLite is delivered as source code only, for inclusion directly in the users' test projects. It will not suffer the weight of NUnit features like extensibility, a gui, multi-threading, use of separate AppDomains, etc. All these features have their place but they can generally be dispensed with in resource-limited situations or when the tests must run in some special environment.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
The NUnitLite codebase is completely separate from NUnit, although obviously inspired by it. Features added to one pof the two products will not automatically be incorporated in the other.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
NUnitLite will initially support Microsoft .Net, Mono and the .Net compact framework.&lt;br/&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;/p&gt;
&lt;p&gt;
Discuss this page: &lt;a href="http://www.codeplex.com/Project/DisplayThread.aspx?ProjectName=NUnitLite&amp;ForumId=52&amp;ThreadId=43"&gt;NUnitLite Vision&lt;/a&gt;&lt;br/&gt;
&lt;br/&gt;
&lt;/p&gt;
</description><author>cpoole</author><pubDate>Tue, 29 Aug 2006 20:52:07 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Vision 20060829085207P</guid></item><item><title>UPDATED WIKI: Home</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=Home&amp;version=9</link><description>*Welcome to the NUnitLite Project*

*NUnitLite* is a a lightweight test framework for .Net, based on a subset of NUnit's features. It will use minimal resources and will run under .Net 1.0, 1.1 and 2.0, Mono 1.0 and 2.0 profiles and the versions 1 and 2 of the compact framework. 

NUnitLite is an Open Source project, available under the Open Source License ("OSL") 3.0.

*Why an NUnitLite?*

Since it's introduction, *NUnit* has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes. For example, *NUnit* creates an AppDomain and loads tests into it. Most applications run perfectly well in this environment, but a very few simply have to run in the primary AppDomain in order to work correctly.

Basically, we want *NUnitLite* to be a very simple *NUnit*, one that could be included as source right with the tests themselves. It should implement a subset of the features of full *NUnit*. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of *NUnit* itself.

The name *NUnitLite* is, of course, inspired by Mike Feathers' *CppUnitLite*.

*Status*

Right now, we're getting organized. The initial *NUnitLite* team will be drawn from the *NUnit* developers. Once we get started, we may put out a call for more members. Key pages to watch and contribute to at this point are

* [121] - our high-level vision of what we want to build
* [123] - our list of features for NUnitLite</description><author>cpoole</author><pubDate>Sat, 03 Jun 2006 03:44:42 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20060603034442A</guid></item><item><title>UPDATED WIKI: Home</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=Home&amp;version=8</link><description>*Welcome to the NUnitLite Home Page*

This is the home page for *NUnitLite*, a lightweight unit-testing framework that works very much like *NUnit*.

*Why an NUnitLite?*

Since it's introduction, *NUnit* has continued to add more features every year. It's getting a bit complicated - too complicated for some purposes. For example, *NUnit* creates an AppDomain and loads tests into it. Most applications run perfectly well in this environment, but a very few simply have to run in the primary AppDomain in order to work correctly.

Basically, we want *NUnitLite* to be a very simple *NUnit*, one that could be included as source right with the tests themselves. It should implement a subset of the features of full *NUnit*. It can also serve as a test bed for a few new approaches that will probably find their way into the next version of *NUnit* itself.

The name *NUnitLite* is, of course, inspired by Mike Feathers' *CppUnitLite*.

*Status*

Right now, we're getting organized. The initial *NUnitLite* team will be drawn from the *NUnit* developers. Once we get started, we may put out a call for more members. Key pages to watch and contribute to at this point are

* [121] - our high-level vision of what we want to build
* [123] - our list of features for NUnitLite</description><author>cpoole</author><pubDate>Tue, 23 May 2006 07:30:32 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: Home 20060523073032A</guid></item><item><title>UPDATED WIKI: NUnitLite Features</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Features&amp;version=11</link><description>!!! NUnitLite Features

*Writing Tests*

The programmer can identify classes that contain tests by use of the TestFixture atttribute. Within such a class, NUnitLite recognizes methods identified with the Test, SetUp or TearDown attribute and interprets them in the same way as full NUnit.

The programmer expresses expected test conditions using static methods of the class Assert. The existing function of current NUnit Assert methods will be supported, subject to the capabilities of the target platforms, but the exact syntax may be changed and later folded back into NUnit.

Programmers will be able to extend Assert by creating classes that implement specific tests.

*Running Tests*

Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests.

Tests (both fixtures and test cases) are executed in the order found, without any guarantees of ordering

A separate instance of the fixture object is created for each test case executed by NUnitLite.

Test results are available through an API or may be saved as XML.</description><author>cpoole</author><pubDate>Tue, 23 May 2006 07:27:15 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Features 20060523072715A</guid></item><item><title>UPDATED WIKI: NUnitLite Stories</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Stories&amp;version=10</link><description>!!! NUnitLite User Stories

*Writing Tests*

The programmer can identify classes that contain tests by use of the TestFixture atttribute. Within such a class, NUnitLite recognizes methods identified with the Test, SetUp or TearDown attribute and interprets them in the same way as full NUnit.

The programmer expresses expected test conditions using static methods of the class Assert. The existing function of current NUnit Assert methods will be supported, subject to the capabilities of the target platforms, but the exact syntax may be changed and later folded back into NUnit.

Programmers will be able to extend Assert by creating classes that implement specific tests.

*Running Tests*

Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests.

Tests (both fixtures and test cases) are executed in the order found, without any guarantees of ordering

A separate instance of the fixture object is created for each test case executed by NUnitLite.

Test results are available through an API or may be saved as XML.</description><author>cpoole</author><pubDate>Sat, 20 May 2006 18:13:19 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Stories 20060520061319P</guid></item><item><title>UPDATED WIKI: NUnitLite Stories</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Stories&amp;version=9</link><description>!!! NUnitLite User Stories

*Writing Tests*

The programmer can identify classes that contain tests by use of the TestFixture atttribute. Within such a class, NUnitLite recognizes methods identified with the Test, SetUp or TearDown attribute and interprets them in the same way as full NUnit.

The programmer expresses expected test conditions using static methods of the class Assert. The existing function of current NUnit Assert methods will be supported, subject to the capabilities of the target platforms, but the exact syntax may be changed and later folded back into NUnit.

Programmers will be able to extend Assert by creating classes that implement specific tests.

*Running Tests*

Tests are loaded as a list of fixtures, without any additional hierarchy. Each fixture contains it's tests.

Tests (both fixtures and test cases) are executed in the order found, without any guarantees of ordering

A separate instance of the fixture object is created for each test case executed by NUnitLite.

*Platform Support*</description><author>cpoole</author><pubDate>Sat, 20 May 2006 18:10:43 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Stories 20060520061043P</guid></item><item><title>UPDATED WIKI: NUnitLite Vision</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Vision&amp;version=15</link><description>!!! The NUnitLite Vision

NUnitLite will be a lightweight test framework for .Net, implementing a limited subset of NUnit's features. It will use minimal resources and be suitable for execution on various classes of devices.

*Features of NUnitLite* (1)

* Like NUnit, NUnitLite is a unit-testing framework, primarily oriented toward TDD.
* NUnitLite is intended to be a subset of NUnit. We may experiment with some new syntax for later inclusion in NUnit itself.
* NUnitLite will be delivered as a set of source files implementing a test loading and running API.
* NUnitLite will initially support Microsoft .Net, Mono and the .Net Compact Framework.

*NUnit Features Not Planned for NUnitLite*

* A Gui test runner. (2)
* Loading of mulitple test assemblies in one run.
* Use of a separate AppDomain for running tests
* Automatic reloading of changed tests
* Higher-level Suites (above fixtures) and higher-level SetUp and TearDown
* Extensibility features

*Notes*
# See [123] for more detailed breakout of features.
# Future versions of NUnit may be extended to load NUnitLite tests.

Discuss this page: [discussion:43]</description><author>cpoole</author><pubDate>Sat, 20 May 2006 18:08:57 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Vision 20060520060857P</guid></item><item><title>UPDATED WIKI: NUnitLite Stories</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Stories&amp;version=8</link><description>!!! NUnitLite User Stories

*Writing Tests*

The programmer can identify classes that contain tests by use of the TestFixture atttribute. Within such a class, NUnitLite recognizes methods identified with the Test, SetUp or TearDown attribute and interprets them in the same way as full NUnit.

The programmer expresses expected test conditions using static methods of the class Assert. The existing function of current NUnit Assert methods will be supported, subject to the capabilities of the target platforms, but the exact syntax may be changed and later folded back into NUnit.

Programmers will be able to extend Assert by creating classes that implement specific tests.

*Running Tests*

A separate instance of the fixture object is created for each test case executed by NUnitLite.

*Platform Support*</description><author>cpoole</author><pubDate>Sat, 20 May 2006 18:07:00 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Stories 20060520060700P</guid></item><item><title>UPDATED WIKI: NUnitLite Stories</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Stories&amp;version=7</link><description>!!! NUnitLite User Stories

*Writing Tests*

The programmer can identify classes that contain tests by use of the TestFixture atttribute. Within such a class, NUnitLite recognizes methods identified with the Test, SetUp or TearDown attribute and interprets them in the same way as full NUnit.

The programmer expresses expected test conditions using static methods of the class Assert model of NUnit. The existing function of current NUnit Assert methods will be supported, subject to the capabilities of the target platforms. The syntax may be changed.

Programmers will be able to extend Assert by creating classes that implement specific tests.

*Running Tests*

A separate instance of the fixture object is created for each test case executed by NUnitLite.

*Platform Support*</description><author>cpoole</author><pubDate>Sat, 20 May 2006 18:05:33 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Stories 20060520060533P</guid></item><item><title>UPDATED WIKI: NUnitLite Stories</title><link>http://www.codeplex.com/Wiki/View.aspx?ProjectName=NUnitLite&amp;title=NUnitLite Stories&amp;version=6</link><description>This page lists user stories for NUnitLite. Please enter each story as a separate paragraph. Project members, please edit. Others, your comments are welcome.

*Writing Tests*

Users may write tests using the following subset of NUnit attributes:
* TestFixture
* Test
* SetUp
* TearDown

Users may express expected test conditions using the Assert model of NUnit.  All current Assert methods from NUnit will be made available but none of the extended Asserters will be.

Users may extend the Assert model with their own Asserts. Depending on how we implement Assert, it may be in the same way as is now done in NUnit or it may use another mechanism.

*Running Tests*

*Platform Support*</description><author>cpoole</author><pubDate>Sat, 20 May 2006 18:04:56 GMT</pubDate><guid isPermaLink="false">UPDATED WIKI: NUnitLite Stories 20060520060456P</guid></item></channel></rss>