<html><head><title>TestDriven.NET - Release Notes</title>
<style>
<!--
.FogBugzReleaseNotes { font-family: Verdana,Arial,sans-serif }
.FogBugzReleaseNotes h1 { border-bottom: 1px solid #449; font-size: 1.2em; color: #449; }
.FogBugzReleaseNotes h2 { font-size: 1em; }
.FogBugzReleaseNotes p { font-family: Georgia,'Times New Roman',serif; margin-left: 0.5in; font-size: 0.9em; }
.FogBugzFooter { font-size: 10px; text-align:center }
-->
</style></head><body>
<div class="FogBugzReleaseNotes">
<h1>Release Notes - TestDriven.NET: 2.18</h1>
<h2>1605: Add support for NUnit 2.5 Beta 1</h2> <p>NUnit 2.5 Beta can be found in the 'Program Files\TestDriven.NET 2.0\NUnit\2.5' folder.</p>
<h2>1606: Add support for targeting generic test fixtures with NUnit 2.5</h2> <p>Added support for targeting generic test fixtures. See <a href="http://nunit.com/index.php?p=testFixture&r=2.5">here</a> for documentation about creating generic fixtures.</p>
<h2>1607: Add support for targeting static test fixtures with NUnit 2.5</h2> <p>Added support for targeting static tests on attributeless static text fixtures. This is particularly useful when writing F# unit tests (where there is no explicit fixture class).</p>
<h2>1603: Only attempt to execute projects that reference a know test framework assembly</h2> <p>When executing all tests in a solution/solution folder, only attempt to execute projects that reference a known test framework assembly. This results in faster execution and eliminates 'skipped' test runs.</p>
<h2>1608: Add automatic support for 64-bit test projects when using different test runner plugins</h2> <p>It is no longer necessary to register test runner plugins under the 32 and 64-bit registry roots when installing for all users (under HKLM). This was a problem for some versions of xUnit and MbUnit.</p>
<h2>1609: Only use the highest priority plugin for a given test framework</h2> <p>If there are multiple plugins installed that can handle a particular test framework (e.g. both xUnit and Gallio register for 'xunit.dll'), only the highest priority runner will be given the chance to execute the tests. This allows ah-hoc tests to be executed when a project also contains xUnit tests.</p>
<h2>1610: Test runners must specify which test framework assembly they support</h2> <p>Test runners must now specify which test framework assembly (e.g. 'nunit.framework' / 'MbUnit.Framework') they support using the 'TargetFrameworkAssemblyName' registry key. This allows non-test projects to be quickly skipped when executing all tests in a solution.</p>
<h2>1604: Drop support for Visual Studio .Net 2002</h2> <p>I've decided to drop support for VS.NET 2002/.NET 1.0 since .NET 1.0 isn't installable on my 64-bit development machine. At this point I believe it's more important for me to dog food x64 support than to maintain legacy support for .NET 1.0.</p>
</div>
<div class="FogBugzReleaseNotes">
<h1>Release Notes - TestDriven.NET: 2.17</h1>
<h2>1598: Add support for Visual Studio 2010</h2> <p>Test runner, code coverage and 'Go To Reflector' functionality now works with Visual Studio 2010/.NET 4.0.</p>
<h2>1593: Add support for Silverlight 2.0 RTM</h2> <p>Use 'Test With > Silverlight' to execute public ad-hoc tests with the Silverlight CoreCLR. This feature is compatible with Silverlight 2.0 RTM and Beta versions.</p>
<h2>1599: Execute tests in namespace using 'Solution Explorer' folder</h2> <p>When all classes in a solution folder belong to the same namespace, TestDriven.Net will execute all tests in the namespace as a single test run rather than as individual test fixtures.</p>
<h2>1592: Save keyboard shortcuts</h2> <p>Preserve keyboard shortcuts when new version of TestDriven.Net is installed. This will work when updating TestDriven.Net 2.17 and higher.</p>
<h2>1595: Add options pane to view test runners</h2> <p>You can view installed test runners under 'Tools > Options... > TestDriven.Net > Test Runners'. A future version will allow you to enable/disable them.</p>
<h2>1590: Look for unit testing framework assembly in target directory and/or target assembly references</h2> <p>This better supports extensible test frameworks like MbUnit or xUnit where their framework assembly ('MbUnit.Framework' or 'xunit') isn't necessarily referenced directly by the test assembly.</p>
</div>
<div class="FogBugzReleaseNotes">
<H1>Release Notes - TestDriven.NET: 2.16</H1>
<H2>1585: Add support for test categories</H2> <P>Categories of test can be included or excluded via the TestDriven.Net options pane (this feature works for NUnit tests).</P>
<H2>1580: Add 'Go To Reflector' support for F#</H2> <P>'Go To Reflector' now works on F# projects, modules, parameterless methods and properties.</P>
<H2>1581: Add support for executing parameterless F# methods</H2> <P>F# methods can be executed as ad-hoc tests or via a unit testing framework that supports static test methods (e.g. xUnit).</P>
<H2>1582: Add support for evaluating F# properties</H2> <P>You can now use 'Run Test(s)' on F# properties to evaluate them.</P>
<H2>1587: Always display console output/error and test runner messages</H2> <P>Test runner generated messages and console output will now be displayed when running all tests in a project/solution.</P>
<H2>1588: Optionally display trace/debug output when running all tests in project/solution</H2> <P>By default trace/debug output isn't displayed when executing all tests in a project/solution. This behaviour can be modified via the TesDriven.Net options pane.</P>
<H2>1586: Add support for test runners that aren't hosted in a new app domain</H2> <P>This is a new extensibility point for test runners that want to manage their own test process/app domain (future versions of Gallio will use this).</P>
</div>
<div class="FogBugzReleaseNotes">
<h1>Release Notes - TestDriven.NET: 2.15</h1>
<h2>1576: Make caching of test process between test runs an option</h2> <p>See 'Tools\Options...\TestDriven.Net' for new option</p>
<h2>1577: Make hiding of output when running all tests in project/solution an option</h2> <p>See 'Tools\Options...\TestDriven.Net' for new option</p>
<h2>1578: Add support for NUnit 2.4.8</h2> <p>NUnit 2.4.8 can now be found in 'NUnit\2.4' directory</p>
</div>
<div class="FogBugzReleaseNotes">
<h1>Release Notes - TestDriven.NET: 2.14</h1>
<h2>1381: Add support for Silverlight 2 Beta 2</h2> <p>'Test With > Silverlight' now supports Silverlight 2 Beta 2.</p>
<h2>1388: 'Test With > Team Coverage' isn't visible in VS2008 Team Edition</h2> <p>Team Coverage is now supported on a clean VS2008 Team Edition install.</p>
<h2>1390: Honour the solution 'Configuration Manager' project 'Build' settings</h2> <p>When
running all tests in a solution, only projects with 'Build' checked in
the 'Configuration Manager' will be built and executed.</p>
<h2>1344: Add support for Gallio's "Icarus" GUI</h2> <p>When Gallio is installed, 'Test With > Gallio Icarus' should appear on project context menu.</p>
<h2>1379: Run all tests in Solution not working with Solution Folders</h2> <p>Tests in solution folders will now be executed.</p>
</div>
<div class="FogBugzReleaseNotes">
<h1>Release Notes - TestDriven.NET: 2.13</h1>
<h2>1341: Add support for Silverlight 2 Beta 1</h2> <p>Running 'ad-hoc' public methods now works with Silverlight 2.0 Beta 1.</p>
<h2>1342: Add support for NUnit 2.4.7</h2> <p>Updated NUnit test runner to target NUnit 2.4.7.</p>
<h2>1343: Include NUnit RowTest Extension in package</h2> <p>Andr
