nunit
/
nunit.org
зеркало из
1
0
Форкнуть 0
Код Задачи Пакеты Проекты Релизы Вики Активность

Remove VS Adapter from legacy documentation

This commit is contained in:
Charlie Poole 2017-04-24 16:33:34 -07:00
Родитель 22f5b95a6c
Коммит a7cea4482d
18 изменённых файлов: 0 добавлений и 1211 удалений
Показать статистику Скачать Patch файл Скачать Diff файл Показать все файлы Свернуть все файлы

2
docs/2.6.1/sub_menu.txt
Просмотреть файл

@ -113,7 +113,5 @@ docHome,NUnit 2.6.1
releaseBreakdown,Release Breakdown
samples
license
vsTestAdapter,NUnit Test Adapter
vsTestAdapterLicense,License

1
docs/2.6.1/vsTestAdapter.html
Просмотреть файл

@ -1 +0,0 @@
<?php unchangedSince("2.6") ?>

28
docs/2.6.1/vsTestAdapterLicense.html
Просмотреть файл

@ -1,28 +0,0 @@
<h2>License - NUnit Test Adapter for Visual Studio 11</h2>
<p><b>Copyright &copy; 2012 Charlie Poole</b>
<p>Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
<p>The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
<h4>Notice</h4>
<p>NUnit 2.6 assemblies distributed with this adapter are subject to the
<?php echo nunit_doc_link("license", "NUnit license") ?>.

5
docs/2.6.2/sub_menu.txt
Просмотреть файл

@ -114,8 +114,3 @@ docHome,NUnit 2.6.2
releaseBreakdown,Release&nbsp;Breakdown
samples
license
vsTestAdapter,NUnit&nbsp;Test&nbsp;Adapter
vsTestAdapterLicense,License
vsTestAdapterReleaseNotes,Release&nbsp;Notes

125
docs/2.6.2/vsTestAdapter.html
Просмотреть файл

@ -1,125 +0,0 @@
<h2>NUnit Test Adapter for Visual Studio 2012 and 2013</h2>
<p>The NUnit Test Adapter allows you to run NUnit tests inside
Visual Studio. The current release, version 0.96, is designed to work
with Studio 2012 RTM, Update 1-3, and with Visual Studio 2013 Preview. Some features are not available under
the RTM.
<p>Note that Releases of Visual Studio prior to VS 2012 did not have the
ability to directly run tests built with Open Source testing frameworks
like NUnit.
<h3>Installation</h3>
<p>From version 0.95 there are two ways of installing the adapter within Visual Studio. See Note 1 how to choose.
<ol>
<li>Use the Extension Manager</li>
<li>Add it as a Nuget package to your solution. (New in 0.95, require Update 1 or higher)</li>
</ol>
<p>To install the NUnit Test Adapter using the
Extension Manager, follow these steps:
<ol>
<li>From within Visual Studio 2012 or 2013, select Tools | Extension Manager.
<li>In the left panel of the Extension Manager, select Online Extensions.
<li>Locate (search for) the NUnit Test Adapter in the center panel and highlight it.
<li>Click 'Download' and follow the instructions.
</ol>
<p>Use the Extension Manager to ensure that the NUnit Test Adapter is enabled.
<p>
To add it is a Nuget package, you must have an active solution, then follow these steps:
<ol>
<li>From Tools menu, use Library Package Manager, select Manage NuGet packages for solution
<li>In the left panel, select Online
<li>Locate (search for) NUnit Test Adapter in the center panel and highlight it
<li>You will find two packages, one without framework and one with framework. See notes below for which to choose.
<li>Click 'Install'
<li>In the "Select Projects" dialog, you need to select at least one project to add the adapter to, see notes below.
</ol>
</p>
<h4>Note 1: How to choose between Extension and NuGet package</h4>
<p>
The Extension will apply to Visual Studio itself, and will work for all projects you use. All users of your solution needs to install the Extension. If you use TFS Build you must also install the extension to the build system there.<br />
The Package will apply to the solution, and will work for any other user too, as it follows the solution, but requires the user to have Update 1 or above. It will also work for any TFS2012 Update 1 or above server build, including TF Service and requires no further installation.
</p>
<h4>Note 2: Choosing NuGet package</h4>
<p>
The adapter packages come with and without the NUnit framework. If you have only one test project you can choose the one with framework, that saves you from having to install both the NUnit package and the Adapter package.
If you have multiple test projects you need to install the NUnit framework for all of these, but only one of these need the adapter, then choose the adapter package without framework. Installing the adapter for multiple projects will do no harm.
</p>
<h3>Usage</h3>
<p>In preparation for using the test adapter, make sure that the Unit
Test Explorer is shown in your window. If you don't see it, use
the menu ( <b>Test | Windows | Test Explorer</b> ) to show it and position
the window where you would like it within Visual Studio.
<div class="screenshot-left">
<?php echo nunit_doc_img( "nunitTestAdapter.png" ) ?>
</div>
<p>When you initially open a solution, no tests will be displayed.
After compiling the assemblies in the solution, Visual Studio will
interact with the NUnit Test Adapter to discover tests and a list
of them will be shown in the Test Explorer.
<p>Click on <b>Run All</b> in the Test Explorer to run
all the tests. You may also select one or more tests in the list and
run them by right-clicking and using the context menu. The context menu
also contains entries for debugging tests and for navigating to the source
code of a test.
<p>Tests may be grouped by Duration and Outcome under VS2012 RTM and also
by Traits and Project using Update 1, and Class using Update 2.&nbsp; NUnit translates any Categories
and Properties used on your tests to Visual Studio as Traits.
<p>Tests may be filtered in Visual Studio under Update 1 by Trait, Project, Error Message,
File Path, Fully Qualified Name, Output and Outcome. Use the search
edit box at the top of the list of tests to specify a filter.
<p>Tests may be organized by play lists in Visual Studio under Update 2. Playlists is more or less equal to the old test lists from VS 2010.
<p>Parametrized tests, like NUnits data driven tests, will show up as seperate test cases for each set of parameters.
<h3>Known Problems</h3>
<ol>
<li><p>There is no test status in Visual Studio corresponding to NUnit's
<b>Inconclusive</b> result, so tests with this result are reported as
<b>Not Run</b>. Click on the individual test to see the result.
<li><p>Grouping by fixture is not yet available.in Visual Studio.
<li><p>Theories are reported as individual cases, rather as a single unit.
<li><p>Startup performance is substantially improved but is still slower
than using NUnit directly.
<li><p>A VSIX adapter of older version will be used regardless of version of NuGet adapter.<br /> Workaround: Make sure you have upgraded VSIX adapter to latest version, or uninstalled it if you have NuGet adapter in a solution.
The 0.95 and later coming versions will output their version number in the Output window under Tests, any older versions will not have any version number there.
</ol>
<h3>
Further information
</h3>
<p>
For more information see the blogs by <a href="http://nunit.com/blogs/" target="_blank">Charlie Poole</a> and <a href="http://geekswithblogs.net/terje/Default.aspx" target="_blank">Terje Sandstrom</a> <br />
Also see the following MSDN ALM blog post:
<ol>
<li><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/11/part-3-unit-testing-with-traits-and-code-coverage-in-visual-studio-2012-using-the-tfs-build-and-the-new-nuget-adapter-approach.aspx" target="_blank">Part 3: Unit testing with Traits and code coverage in Visual Studio 2012 using the TFS Build – and the new NuGet adapter approach</a></li>
<li><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/20/part-2-using-traits-with-different-test-frameworks-in-the-unit-test-explorer.aspx" target="_blank">Part 2–Using Traits with different test frameworks in the Unit Test Explorer</a>
<li><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/09/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1-using-traits-in-the-unit-test-explorer.aspx" target="_blank">How to manage unit tests in Visual Studio 2012 Update 1 : Part 1–Using Traits in the Unit Test Explorer</a>
</ol>
</p>
<h3>Reporting Problems</h3>
<p>Bugs should be reported using the separate test adapter
<a href="http://bugs.launchpad.net/nunit-vs-adapter" target="_blank">bug tracker</a> on Launchpad.

28
docs/2.6.2/vsTestAdapterLicense.html
Просмотреть файл

@ -1,28 +0,0 @@
<h2>License - NUnit Test Adapter for Visual Studio 2012 and 2013</h2>
<p><b>Copyright &copy; 2012, 2013 Charlie Poole</b>
<p>Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
<p>The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
<h4>Notice</h4>
<p>NUnit 2.6 assemblies distributed with this adapter are subject to the
<?php echo nunit_doc_link("license", "NUnit license") ?>.

159
docs/2.6.2/vsTestAdapterReleaseNotes.html
Просмотреть файл

@ -1,159 +0,0 @@
<style><!--
li { padding-bottom: .5em; }
ul ul li { padding-bottom: 0; }
dt { font-weight: bold }
--></style>
<h3>NUnit Test Adapter for Visual Studio (Beta 6) - Version 0.96.0 - June 28, 2013</h3>
<h4>Features</h4>
<ul>
<li>Support for Visual Studio 2013 Preview added
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1189268 Profile a test will crash with exception
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95.1 - May 28, 2013</h3>
<h4>Features</h4>
<ul>
<li>Test project now uses NUnit nuget package
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1184231 Cannot run or debug tests on VStudio after update 0.95
<li>1074042 Breakpoints ignored when running tests in debug mode
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95 - May 10, 2013</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Update 2 and 3 as well as the RTM and Update 1
<li>Now available as NuGet packages
<li>Improved messages in output window, includes version numbers.
<li>Parametrized tests shows up as seperate test cases
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1155617 Grouping by class name in VS 2012 doesn't work
<li>1165359 Exception after building Coded UI test
<li>1116747 vstest.executionengine.x86.exe does not terminate
<li>1093178 Eliminate unnecessary files from VSIX
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 4) - Version 0.94 - December 22, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Update 1 as well as the RTM.
<li>Supports filtering and sorting tests by Traits under Update 1.
<li>Supports use of standard filter expressions when running under TFS Update 1.
<li>NUnit Categories specified on the fixture class are now recognized and honored.
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1074891 Can't test multiple assemblies referencing different NUnit versions
<li>1075893 Test execution fails if solution contains native C++ project
<li>1076012 No source information found for async test methods
<li>1087629 TestFixture Category not being recognised as traits in VS2012 update 1
<li>1091020 Adapter doesnt support TFS Build traits/test case filtering
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3-2) - Version 0.93.2 - November 2, 2012</h3>
<h4>Bug Fixes</h4>
<ul>
<li>1074544 Failures in Test Discovery not reporting sufficient information
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3-1) - Version 0.93.1 - October 26, 2012</h3>
<h4>Bug Fixes</h4>
<ul>
<li>1072150 NUnit adapter 0.93 won't run selected tests
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3) - Version 0.93 - October 24, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 RTM. Some features require the November CTP update.
<li>The adapter now uses NUnit 2.6.2. Among other things, this allows us to support async test methods. See the NUnit <?php echo nunit_doc_link( "releaseNotes", "Release Notes" ) ?> for more info.
<li>Source file and line number can now be found for test cases that have an alternate name set.
<li>Console output from tests is now displayed in the Visual Studio Output window.
<li>TestFixtureSetUp and TestFixtureTearDown errors are now displayed in the Output window.
<li>The caret line (------^) is no longer displayed in the IDE since it depends on use of a fixed font.
<li>Tests may now be grouped and filtered by Category (only under the November CTP update for VS2012).
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1021144 Text output from tests not displayed in Visual Studio IDE
<li>1033623 Not possible to include or exclude tests based on [Category] attribute Released
<li>1040779 Null reference exception on generic test fixtures
<li>1064620 Support async test methods
<li>1065209 Should call both RecordEnd and RecordResult at end of a test
<li>1065212 Upgrade NUnit to 2.6.2
<li>1065223 Error messages assume a fixed font, but don't get one
<li>1065225 No display for TestFixtureSetUp/TearDown or SetUpFixture errors
<li>1065254 Cannot open test from Test Explorer for tests in a Parameterized Test Fixture
<li>1065306 Generic Fixtures aren't discovered.
<li>1066393 Unable to display source for testcases with an alternate name set
<li>1066518 Executed fast test appears in Not Run category in Test Explorer
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 2) - Version 0.92 - May 3, 2012
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Release Candidate
<li>Uses NUnit 2.6
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>992837 Unable to Debug using VS Test Adapter
<li>994146 Can't run tests under .NET 2.0/3.5
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 1) - Version 0.91 - February 29, 2012
<h4>Features</h4>
<ul>
<li>Built against Visual Studio 11 Beta 1
<li>Uses NUnit 2.6
</ul>
<h3>NUnit Test Adapter for Visual Studio (Alpha) - Version 0.90 - February 21, 2012
<h4>Features</h4>
<ul>
<li>First release of the test adapter. Compatible with the Visual Studio 11 Developer Preview.
<li>Uses NUnit 2.6.
</ul>

4
docs/2.6.3/sub_menu.txt
Просмотреть файл

@ -114,8 +114,4 @@ docHome,NUnit 2.6.3
releaseBreakdown,Release&nbsp;Breakdown
samples
license
vsTestAdapter,NUnit&nbsp;Test&nbsp;Adapter
vsTestAdapterLicense,License
vsTestAdapterReleaseNotes,Release&nbsp;Notes

108
docs/2.6.3/vsTestAdapter.html
Просмотреть файл

@ -1,108 +0,0 @@
<h2>NUnit Test Adapter for Visual Studio</h2>
<p>The NUnit Test Adapter allows you to run NUnit tests inside Visual Studio. The current release, version 1.2, is designed to work with Studio 2012 (All updates), and with Visual Studio 2013 (All updates including Update 3 checked September 2014). Some features are not available under VS2012 RTM.</p>
<p>Note that Releases of Visual Studio prior to VS 2012 did not have the ability to directly run tests built with Open Source testing frameworks like NUnit.</p>
<h2>Installation</h2>
<p>Beginning with version 0.95 there are two ways of installing the adapter within Visual Studio. See Note 1 below for info on how to choose.</p>
<ol>
<li>Use the Extension Manager</li>
<li>Add it as a Nuget package to your solution. (New in 0.95, requires VS 2012 Update 1 or higher)</li>
</ol>
<h3>Installing With the Extension Manager</h3>
<p>To install the NUnit Test Adapter using the Extension Manager, follow these steps:</p>
<ol>
<li>From within Visual Studio 2012 or 2013, select Tools | Extension Manager.</li>
<li>In the left panel of the Extension Manager, select Online Extensions.</li>
<li>Locate (search for) the NUnit Test Adapter in the center panel and highlight it.</li>
<li>Click 'Download' and follow the instructions.</li>
</ol>
<p>Use the Extension Manager to ensure that the NUnit Test Adapter is enabled.</p>
<h3>Installing the Nuget Package</h3>
<p>To add it is a Nuget package, you must have an active solution, then follow these steps:</p>
<ol>
<li>From Tools menu, use Library Package Manager, select Manage NuGet packages for solution</li>
<li>In the left panel, select Online</li>
<li>Locate (search for) NUnit Test Adapter in the center panel and highlight it</li>
<li>You will find two packages, one without framework and one with framework. See note 2 below for which to choose.</li>
<li>Click 'Install'</li>
<li>In the "Select Projects" dialog, you need to select at least one project to add the adapter to, see notes below.</li>
</ol>
<h3>Notes</h3>
<p><strong>Note 1: How to choose between Extension and NuGet package</strong></p>
<p>The Extension will apply to Visual Studio itself, and will work for all projects you use. All users of your solution need to install the Extension. If you use TFS Build you must also install the extension to the build system there.
The Package will apply to the solution, and will work for any other user too, as it follows the solution, but requires the user to have Update 1 or above. It will also work for any TFS2012 Update 1 or above server build, including TF Service and requires no further installation.</p>
<p><strong>Note 2: Choosing NuGet package</strong></p>
<p>The adapter packages come with and without the NUnit framework. If you have only one test project you can choose the one with framework, that saves you from having to install both the NUnit package and the Adapter package. If you have multiple test projects you need to install the NUnit framework for all of these, but only one of these need the adapter, then choose the adapter package without framework. Installing the adapter for multiple projects will do no harm.</p>
<p><strong>Note 3: Choosing both</strong>
This will work, but the Nuget package will be ignored. Since this can be confusing, we don't advise it.</p>
<h2>Usage</h2>
<p>In preparation for using the test adapter, make sure that the Unit Test Explorer is shown in your window. If you don't see it, use the menu ( Test | Windows | Test Explorer ) to show it and position the window where you would like it within Visual Studio.
<div class="screenshot-left">
<?php echo nunit_doc_img("nunitTestAdapter.png") ?>
</div>
<p>When you initially open a solution, no tests will be displayed. After compiling the assemblies in the solution, Visual Studio will interact with the NUnit Test Adapter to discover tests and a list of them will be shown in the Test Explorer.</p>
<p>Click on Run All in the Test Explorer to run all the tests. You may also select one or more tests in the list and run them by right-clicking and using the context menu. The context menu also contains entries for debugging tests and for navigating to the source code of a test.</p>
<p>Tests may be grouped by Duration and Outcome under VS2012 RTM and also by Traits and Project using Update 1, and Class using Update 2. NUnit translates any Categories and Properties used on your tests to Visual Studio as Traits.</p>
<p>Tests may be filtered in Visual Studio under Update 1 by Trait, Project, Error Message, File Path, Fully Qualified Name, Output and Outcome. Use the search edit box at the top of the list of tests to specify a filter.</p>
<p>Tests may be organized by play lists in Visual Studio under Update 2. Playlists are more or less equal to the old test lists from VS 2010.</p>
<p>Parameterized tests will show up as separate test cases for each set of parameters.</p>
<h2>Known Problems</h2>
<ol>
<li>There is no test status in Visual Studio corresponding to NUnit's Inconclusive result, so tests with this result are reported as Not Run. Click on the individual test to see the result.</li>
<li>Grouping by fixture is not yet available.in Visual Studio.</li>
<li>Theories are reported as individual cases, rather as a single unit.</li>
<li>Startup performance is substantially improved but is still slower than using NUnit directly.</li>
<li>A VSIX adapter of older version will be used regardless of version of NuGet adapter.</li>
</ol>
<p>Workaround: Make sure you have upgraded VSIX adapter to latest version, or uninstalled it if you have the NuGet adapter in a solution. The 0.95 and later versions will output their version number in the Output window under Tests, any older versions will not display a version number.</p>
<h2>Issues with other tools</h2>
<ol>
<li>Versions of Resharper earlier than the 8.2 version has an issue with the NuGet adapter, which will prevent NUnit tests from running. Make sure you have updated Reshaper to at version 8.2. </li>
</ol>
<h2>Further information</h2>
<p>For more information see the blogs by <a href="http://nunit.com/blogs/" title="Charlie Poole">Charlie Poole</a> and <a href="http://geekswithblogs.net/terje/Default.aspx">Terje Sandstrom</a>
Also see the following MSDN ALM blog post:</p>
<p><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/11/part-3-unit-testing-with-traits-and-code-coverage-in-visual-studio-2012-using-the-tfs-build-and-the-new-nuget-adapter-approach.aspx">Part 3: Unit testing with Traits and code coverage in Visual Studio 2012 using the TFS Build – and the new NuGet adapter approach</a></p>
<p><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/20/part-2-using-traits-with-different-test-frameworks-in-the-unit-test-explorer.aspx">Part 2–Using Traits with different test frameworks in the Unit Test Explorer</a></p>
<p><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/09/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1-using-traits-in-the-unit-test-explorer.aspx">How to manage unit tests in Visual Studio 2012 Update 1 : Part 1–Using Traits in the Unit Test Explorer</a></p>
<h2>Reporting Problems</h2>
<p>Bugs should be reported using the <a href="https://github.com/nunit/nunit-vs-adapter/issues">issue tracker</a> on Github, </p>

28
docs/2.6.3/vsTestAdapterLicense.html
Просмотреть файл

@ -1,28 +0,0 @@
<h2>License - NUnit Test Adapter for Visual Studio</h2>
<p><b>Copyright &copy; 2012-2014 Charlie Poole</b>
<p>Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
<p>The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
<h4>Notice</h4>
<p>NUnit 2.6 assemblies distributed with this adapter are subject to the
<?php echo nunit_doc_link("license", "NUnit license") ?>.

233
docs/2.6.3/vsTestAdapterReleaseNotes.html
Просмотреть файл

@ -1,233 +0,0 @@
<style><!--
li { padding-bottom: .5em; }
ul ul li { padding-bottom: 0; }
dt { font-weight: bold }
--></style>
<h3>NUnit Test Adapter for Visual Studio (2012, RTM - Update 4, 2013, RTM - Update 3) : Version 1.2 - September 17, 2014</h3>
(Note: Issue numbers now refers to our new home on <a href="https://github.com/nunit/nunit-vs-adapter">Github</a>.)
<h4>Features</h4>
<ul>
<li>Tested for up to VS2013 Update 3</li>
<li>Bugs 39 and 40 : The adapter was unable to run under VS2012. This is now fixed.</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#24 Long-running tests ignored</li>
<li>#34 Adapter causes ArgumentException to be thrown by Microsoft logger proxy's SendMessage method</li>
<li>#37 TestExecution throws Exception System.InvalidOperationException in TFS Build</li>
<li>#38 NUnit only accepts absolute paths to test assembly</li>
<li>#39 VSTest unable to find NUnit tests since 1.1.0.0</li>
<li>#40 NUnit version 1.1.0.0 is broken with test class which ran under 1.0.0.0</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RTM) - Version 1.1 - April 26, 2014</h3>
(Note: Issue numbers now refers to our new home on Github.)
<h4>Features</h4>
<ul>
<li>Support for NUnit 2.6.3</li>
<li>Tested for up to VS2013 Update 2 RC</li>
<li>Shadow copy now disabled by default, see issue #7 Unable to disable shadow copy.</li>
<li>Registry settings added for some customization options, see <a href="https://github.com/nunit/nunit-vs-adapter/wiki/Tips-And-Tricks">Tips and Tricks</a></li>
<li>All code moved to <a href="https://github.com/nunit/nunit-vs-adapter">github</a></li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#13 Category attribute not working with TFS test case filter</li>
<li>#21 Xamarin.iOS Nunit project causes adapter to throw</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RTM) - Version 1.0 - September 12, 2013</h3>
<h4>Features</h4>
<ul>
<li>This is the release version 1.0 of the test adapter.</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1208148 The test result output node is not shown for debug/trace statements</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RC) - Version 0.97 - September 12, 2013</h3>
<h4>Features</h4>
<ul>
<li>This is the release candidate for version 1.0 of the test adapter.</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1208161 NUnit Test Adapter runs [Explicit] unit tests in TFS Build</li>
<li>#1210536 No Source Available for Async Tests</li>
<li>#1165188 Clicking "Run Selected Tests" doesn't show Trace.WriteLine() output</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 6) - Version 0.96 - June 28, 2013</h3>
<h4>Features</h4>
<ul>
<li>Support for Visual Studio 2013 Preview</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1189268 Profile a test will crash with exception</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95.2 - June 7, 2013</h3>
<h4>Bug Fixes</h4>
<ul>
<li>#1188000, adapter dont work with solutions with only .net 2.0/3.5 project</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95.1 Hotfix- May 28, 2013</h3>
<h4>Bug Fixes</h4>
<ul>
<li>Hotfix for debug issue</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95 - May 10, 2013</h3>
<h4>Features</h4>
<ul>
<li>#1174925 Add support for installing the adapter from Nuget</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1155617 Grouping by class name in VS 2012 doesn't work</li>
<li>#1165359 Exception after building Coded UI test</li>
<li>#1116747 vstest.executionengine.x86.exe does not terminate</li>
<li>#1093178 Eliminate unnecessary files from VSIX</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 4) - Version 0.94 - December 22, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Update 1 as well as the RTM.
<li>Supports filtering and sorting tests by Traits under Update 1.
<li>Supports use of standard filter expressions when running under TFS Update 1.
<li>NUnit Categories specified on the fixture class are now recognized and honored.
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1074891 Can't test multiple assemblies referencing different NUnit versions
<li>1075893 Test execution fails if solution contains native C++ project
<li>1076012 No source information found for async test methods
<li>1087629 TestFixture Category not being recognised as traits in VS2012 update 1
<li>1091020 Adapter doesnt support TFS Build traits/test case filtering
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3-2) - Version 0.93.2 - November 2, 2012</h3>
<h4>Bug Fixes</h4>
<ul>
<li>1074544 Failures in Test Discovery not reporting sufficient information
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3-1) - Version 0.93.1 - October 26, 2012</h3>
<h4>Bug Fixes</h4>
<ul>
<li>1072150 NUnit adapter 0.93 won't run selected tests
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3) - Version 0.93 - October 24, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 RTM. Some features require the November CTP update.
<li>The adapter now uses NUnit 2.6.2. Among other things, this allows us to support async test methods. See the NUnit <?php echo nunit_doc_link( "releaseNotes", "Release Notes" ) ?> for more info.
<li>Source file and line number can now be found for test cases that have an alternate name set.
<li>Console output from tests is now displayed in the Visual Studio Output window.
<li>TestFixtureSetUp and TestFixtureTearDown errors are now displayed in the Output window.
<li>The caret line (------^) is no longer displayed in the IDE since it depends on use of a fixed font.
<li>Tests may now be grouped and filtered by Category (only under the November CTP update for VS2012).
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1021144 Text output from tests not displayed in Visual Studio IDE
<li>1033623 Not possible to include or exclude tests based on [Category] attribute Released
<li>1040779 Null reference exception on generic test fixtures
<li>1064620 Support async test methods
<li>1065209 Should call both RecordEnd and RecordResult at end of a test
<li>1065212 Upgrade NUnit to 2.6.2
<li>1065223 Error messages assume a fixed font, but don't get one
<li>1065225 No display for TestFixtureSetUp/TearDown or SetUpFixture errors
<li>1065254 Cannot open test from Test Explorer for tests in a Parameterized Test Fixture
<li>1065306 Generic Fixtures aren't discovered.
<li>1066393 Unable to display source for testcases with an alternate name set
<li>1066518 Executed fast test appears in Not Run category in Test Explorer
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 2) - Version 0.92 - May 3, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Release Candidate
<li>Uses NUnit 2.6
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>992837 Unable to Debug using VS Test Adapter
<li>994146 Can't run tests under .NET 2.0/3.5
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 1) - Version 0.91 - February 29, 2012</h3>
<h4>Features</h4>
<ul>
<li>Built against Visual Studio 11 Beta 1
<li>Uses NUnit 2.6
</ul>
<h3>NUnit Test Adapter for Visual Studio (Alpha) - Version 0.90 - February 21, 2012</h3>
<h4>Features</h4>
<ul>
<li>First release of the test adapter. Compatible with the Visual Studio 11 Developer Preview.
<li>Uses NUnit 2.6.
</ul>

3
docs/2.6.4/sub_menu.txt
Просмотреть файл

@ -114,8 +114,5 @@ docHome,NUnit 2.6.4
releaseBreakdown,Release&nbsp;Breakdown
samples
license
vsTestAdapter,NUnit&nbsp;Test&nbsp;Adapter
vsTestAdapterLicense,License
vsTestAdapterReleaseNotes,Release&nbsp;Notes

107
docs/2.6.4/vsTestAdapter.html
Просмотреть файл

@ -1,107 +0,0 @@
<h2>NUnit Test Adapter for Visual Studio</h2>
<p>The NUnit Test Adapter allows you to run NUnit tests inside Visual Studio. The current release, version 2-0, is designed to work with Studio 2012 (All updates), Visual Studio 2013 (All updates) and Visual Studio 2015 (tested with all pre-releases, checked April 2015). Some features are not available under VS2012 RTM.</p>
<p>Note that Releases of Visual Studio prior to VS 2012 did not have the ability to directly run tests built with Open Source testing frameworks like NUnit.</p>
<h2>Installation</h2>
<p>Beginning with version 0.95 there are two ways of installing the adapter within Visual Studio. See Note 1 below for info on how to choose.</p>
<ol>
<li>Use the Extension Manager</li>
<li>Add it as a Nuget package to your solution. (New in 0.95, requires VS 2012 Update 1 or higher)</li>
</ol>
<h3>Installing With the Extension Manager</h3>
<p>To install the NUnit Test Adapter using the Extension Manager, follow these steps:</p>
<ol>
<li>From within Visual Studio 2012, 2013 or 2015, select Tools | Extension Manager.</li>
<li>In the left panel of the Extension Manager, select Online Extensions.</li>
<li>Locate (search for) the NUnit Test Adapter in the center panel and highlight it.</li>
<li>Click 'Download' and follow the instructions.</li>
</ol>
<p>Use the Extension Manager to ensure that the NUnit Test Adapter is enabled.</p>
<h3>Installing the Nuget Package</h3>
<p>To add it is a Nuget package, you must have an active solution, then follow these steps:</p>
<ol>
<li>From Tools menu, use Library Package Manager, select Manage NuGet packages for solution</li>
<li>In the left panel, select Online</li>
<li>Locate (search for) NUnit Test Adapter in the center panel and highlight it</li>
<li>You will find two packages, one without framework and one with framework. See note 2 below for which to choose.</li>
<li>Click 'Install'</li>
<li>In the "Select Projects" dialog, you need to select at least one project to add the adapter to, see notes below.</li>
</ol>
<h3>Notes</h3>
<p><strong>Note 1: How to choose between Extension and NuGet package</strong></p>
<p>The Extension will apply to Visual Studio itself, and will work for all projects you use. All users of your solution need to install the Extension. If you use TFS Build you must also install the extension to the build system there.
The Package will apply to the solution, and will work for any other user too, as it follows the solution, but requires the user to have Update 1 or above. It will also work for any TFS2012 Update 1 or above server build, including TF Service and requires no further installation.</p>
<p><strong>Note 2: Choosing NuGet package</strong></p>
<p>The adapter packages come with and without the NUnit framework. If you have only one test project you can choose the one with framework, that saves you from having to install both the NUnit package and the Adapter package. If you have multiple test projects you need to install the NUnit framework for all of these, but only one of these need the adapter, then choose the adapter package without framework. Installing the adapter for multiple projects will do no harm.</p>
<p><strong>Note 3: Choosing both</strong>
This will work, but the Nuget package will be ignored. Since this can be confusing, we don't advise it.</p>
<h2>Usage</h2>
<p>In preparation for using the test adapter, make sure that the Unit Test Explorer is shown in your window. If you don't see it, use the menu ( Test | Windows | Test Explorer ) to show it and position the window where you would like it within Visual Studio.
<div class="screenshot-left">
<?php echo nunit_doc_img("nunitTestAdapter.png") ?>
</div>
<p>When you initially open a solution, no tests will be displayed. After compiling the assemblies in the solution, Visual Studio will interact with the NUnit Test Adapter to discover tests and a list of them will be shown in the Test Explorer.</p>
<p>Click on Run All in the Test Explorer to run all the tests. You may also select one or more tests in the list and run them by right-clicking and using the context menu. The context menu also contains entries for debugging tests and for navigating to the source code of a test.</p>
<p>Tests may be grouped by Duration and Outcome under VS2012 RTM and also by Traits and Project using Update 1, and Class using Update 2. NUnit translates any Categories and Properties used on your tests to Visual Studio as Traits.</p>
<p>Tests may be filtered in Visual Studio under Update 1 by Trait, Project, Error Message, File Path, Fully Qualified Name, Output and Outcome. Use the search edit box at the top of the list of tests to specify a filter.</p>
<p>Tests may be organized by play lists in Visual Studio under Update 2. Playlists are more or less equal to the old test lists from VS 2010.</p>
<p>Parameterized tests will show up as separate test cases for each set of parameters.</p>
<h2>Known Problems</h2>
<ol>
<li>There is no test status in Visual Studio corresponding to NUnit's Inconclusive result, so tests with this result are reported as Not Run. Click on the individual test to see the result.</li>
<li>Theories are reported as individual cases, rather as a single unit.</li>
<li>Startup performance is substantially improved but is still slower than using NUnit directly.</li>
<li>A VSIX adapter of older version will be used regardless of version of NuGet adapter.</li>
</ol>
<p>Workaround: Make sure you have upgraded VSIX adapter to latest version, or uninstalled it if you have the NuGet adapter in a solution. The 0.95 and later versions will output their version number in the Output window under Tests, any older versions will not display a version number.</p>
<h2>Issues with other tools</h2>
<ol>
<li>Versions of Resharper earlier than the 8.2 version has an issue with the NuGet adapter, which will prevent NUnit tests from running. Make sure you have updated Reshaper to at version 8.2. </li>
</ol>
<h2>Further information</h2>
<p>For more information see the blogs by <a href="http://nunit.com/blogs/" title="Charlie Poole">Charlie Poole</a> and <a href="http://geekswithblogs.net/terje/Default.aspx">Terje Sandstrom</a>
Also see the following MSDN ALM blog post:</p>
<p><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/11/part-3-unit-testing-with-traits-and-code-coverage-in-visual-studio-2012-using-the-tfs-build-and-the-new-nuget-adapter-approach.aspx">Part 3: Unit testing with Traits and code coverage in Visual Studio 2012 using the TFS Build – and the new NuGet adapter approach</a></p>
<p><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/20/part-2-using-traits-with-different-test-frameworks-in-the-unit-test-explorer.aspx">Part 2–Using Traits with different test frameworks in the Unit Test Explorer</a></p>
<p><a href="http://blogs.msdn.com/b/visualstudioalm/archive/2012/11/09/how-to-manage-unit-tests-in-visual-studio-2012-update-1-part-1-using-traits-in-the-unit-test-explorer.aspx">How to manage unit tests in Visual Studio 2012 Update 1 : Part 1–Using Traits in the Unit Test Explorer</a></p>
<h2>Reporting Problems</h2>
<p>Bugs should be reported using the <a href="https://github.com/nunit/nunit-vs-adapter/issues">issue tracker</a> on Github, </p>

28
docs/2.6.4/vsTestAdapterLicense.html
Просмотреть файл

@ -1,28 +0,0 @@
<h2>License - NUnit Test Adapter for Visual Studio</h2>
<p><b>Copyright &copy; 2012-2015 Charlie Poole</b>
<p>Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
<p>The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
<h4>Notice</h4>
<p>NUnit 2.6 assemblies distributed with this adapter are subject to the
<?php echo nunit_doc_link("license", "NUnit license") ?>.

255
docs/2.6.4/vsTestAdapterReleaseNotes.html
Просмотреть файл

@ -1,255 +0,0 @@
<style><!--
li { padding-bottom: .5em; }
ul ul li { padding-bottom: 0; }
dt { font-weight: bold }
--></style>
<h3>NUnit Test Adapter for Visual Studio - Version 2.0 - April 1, 2015</h3>
(Note: Issue numbers now refers to our new home on Github.)
<h4>Features</h4>
<ul>
<li>Tested for up to VS2015 Pre-release CTP 6</li>
<li>Updated to use NUnit 2.6.4</li>
<li>Adapter does not try to discover tests if the nunit.framework version is 3.0 or greater</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#61 Confusing NUnit version message made clearer</li>
<li>#62 Adapter uses shadowcopy setting in discoverer but not in the executor</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RTM) - Version 1.2 - September 17, 2014</h3>
(Note: Issue numbers now refers to our new home on Github.)
<h4>Features</h4>
<ul>
<li>Tested for up to VS2013 Update 3</li>
<li>Bugs 39 and 40 was inability to run under VS2012. This is now fixed.</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#24 Long-running tests ignored</li>
<li>#34 Adapter causes ArgumentException to be thrown by Microsoft logger proxy's SendMessage method</li>
<li>#37 TestExecution throws Exception System.InvalidOperationException in TFS Build</li>
<li>#38 NUnit only accepts absolute paths to test assembly</li>
<li>#39 VSTest unable to find NUnit tests since 1.1.0.0</li>
<li>#40 NUnit version 1.1.0.0 is broken with test class which ran under 1.0.0.0</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RTM) - Version 1.1 - April 26, 2014</h3>
(Note: Issue numbers now refers to our new home on Github.)
<h4>Features</h4>
<ul>
<li>Support for NUnit 2.6.3</li>
<li>Tested for up to VS2013 Update 2 RC</li>
<li>Shadow copy now disabled by default, see issue #7 Unable to disable shadow copy.</li>
<li>Registry settings added for some customization options, see <a href="https://github.com/nunit/nunit-vs-adapter/wiki/Tips-And-Tricks">Tips and Tricks</a></li>
<li>All code moved to <a href="https://github.com/nunit/nunit-vs-adapter">github</a></li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#13 Category attribute not working with TFS test case filter</li>
<li>#21 Xamarin.iOS Nunit project causes adapter to throw</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RTM) - Version 1.0 - September 12, 2013</h3>
<h4>Features</h4>
<ul>
<li>This is the release version 1.0 of the test adapter.</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1208148 The test result output node is not shown for debug/trace statements</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (RC) - Version 0.97 - September 12, 2013</h3>
<h4>Features</h4>
<ul>
<li>This is the release candidate for version 1.0 of the test adapter.</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1208161 NUnit Test Adapter runs [Explicit] unit tests in TFS Build</li>
<li>#1210536 No Source Available for Async Tests</li>
<li>#1165188 Clicking "Run Selected Tests" doesn't show Trace.WriteLine() output</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 6) - Version 0.96 - June 28, 2013</h3>
<h4>Features</h4>
<ul>
<li>Support for Visual Studio 2013 Preview</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1189268 Profile a test will crash with exception</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95.2 - June 7, 2013</h3>
<h4>Bug Fixes</h4>
<ul>
<li>#1188000, adapter dont work with solutions with only .net 2.0/3.5 project</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95.1 Hotfix- May 28, 2013</h3>
<h4>Bug Fixes</h4>
<ul>
<li>Hotfix for debug issue</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 5) - Version 0.95 - May 10, 2013</h3>
<h4>Features</h4>
<ul>
<li>#1174925 Add support for installing the adapter from Nuget</li>
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>#1155617 Grouping by class name in VS 2012 doesn't work</li>
<li>#1165359 Exception after building Coded UI test</li>
<li>#1116747 vstest.executionengine.x86.exe does not terminate</li>
<li>#1093178 Eliminate unnecessary files from VSIX</li>
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 4) - Version 0.94 - December 22, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Update 1 as well as the RTM.
<li>Supports filtering and sorting tests by Traits under Update 1.
<li>Supports use of standard filter expressions when running under TFS Update 1.
<li>NUnit Categories specified on the fixture class are now recognized and honored.
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1074891 Can't test multiple assemblies referencing different NUnit versions
<li>1075893 Test execution fails if solution contains native C++ project
<li>1076012 No source information found for async test methods
<li>1087629 TestFixture Category not being recognised as traits in VS2012 update 1
<li>1091020 Adapter doesnt support TFS Build traits/test case filtering
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3-2) - Version 0.93.2 - November 2, 2012</h3>
<h4>Bug Fixes</h4>
<ul>
<li>1074544 Failures in Test Discovery not reporting sufficient information
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3-1) - Version 0.93.1 - October 26, 2012</h3>
<h4>Bug Fixes</h4>
<ul>
<li>1072150 NUnit adapter 0.93 won't run selected tests
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 3) - Version 0.93 - October 24, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 RTM. Some features require the November CTP update.
<li>The adapter now uses NUnit 2.6.2. Among other things, this allows us to support async test methods. See the NUnit <?php echo nunit_doc_link( "releaseNotes", "Release Notes" ) ?> for more info.
<li>Source file and line number can now be found for test cases that have an alternate name set.
<li>Console output from tests is now displayed in the Visual Studio Output window.
<li>TestFixtureSetUp and TestFixtureTearDown errors are now displayed in the Output window.
<li>The caret line (------^) is no longer displayed in the IDE since it depends on use of a fixed font.
<li>Tests may now be grouped and filtered by Category (only under the November CTP update for VS2012).
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>1021144 Text output from tests not displayed in Visual Studio IDE
<li>1033623 Not possible to include or exclude tests based on [Category] attribute Released
<li>1040779 Null reference exception on generic test fixtures
<li>1064620 Support async test methods
<li>1065209 Should call both RecordEnd and RecordResult at end of a test
<li>1065212 Upgrade NUnit to 2.6.2
<li>1065223 Error messages assume a fixed font, but don't get one
<li>1065225 No display for TestFixtureSetUp/TearDown or SetUpFixture errors
<li>1065254 Cannot open test from Test Explorer for tests in a Parameterized Test Fixture
<li>1065306 Generic Fixtures aren't discovered.
<li>1066393 Unable to display source for testcases with an alternate name set
<li>1066518 Executed fast test appears in Not Run category in Test Explorer
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 2) - Version 0.92 - May 3, 2012</h3>
<h4>Features</h4>
<ul>
<li>Works with Visual Studio 2012 Release Candidate
<li>Uses NUnit 2.6
</ul>
<h4>Bug Fixes</h4>
<ul>
<li>992837 Unable to Debug using VS Test Adapter
<li>994146 Can't run tests under .NET 2.0/3.5
</ul>
<h3>NUnit Test Adapter for Visual Studio (Beta 1) - Version 0.91 - February 29, 2012</h3>
<h4>Features</h4>
<ul>
<li>Built against Visual Studio 11 Beta 1
<li>Uses NUnit 2.6
</ul>
<h3>NUnit Test Adapter for Visual Studio (Alpha) - Version 0.90 - February 21, 2012</h3>
<h4>Features</h4>
<ul>
<li>First release of the test adapter. Compatible with the Visual Studio 11 Developer Preview.
<li>Uses NUnit 2.6.
</ul>

4
docs/2.6/sub_menu.txt
Просмотреть файл

@ -113,7 +113,3 @@ docHome,NUnit 2.6
releaseBreakdown,Release&nbsp;Breakdown
samples
license
vsTestAdapter,NUnit&nbsp;Test&nbsp;Adapter
vsTestAdapterLicense,License

65
docs/2.6/vsTestAdapter.html
Просмотреть файл

@ -1,65 +0,0 @@
<h2>NUnit Test Adapter for Visual Studio 11</h2>
<p>The NUnit Test Adapter allows you to run NUnit tests inside
Visual Studio. The current release, version 0.92, is designed to work
with the Visual Studio 11 Beta Release. Releases of Visual Studio
prior to VS 11 did not have the ability to directly run tests built with
Open Source testing frameworks like NUnit.
<h3>Installation</h3>
<p>The easiest way to install the NUnit Test Adapter is using the
Extension Manager within Visual Studio. Follow these steps:
<ol>
<li>From within Visual Studio 11, select Tools | Extension Manager.
<li>In the left panel of the Extension Manager, select Online Extensions.
<li>Locate the NUnit Test Adapter in the center panel and highlight it.
<li>Click 'Download' and follow the instructions.
</ol>
<p>Use the Extension Manager to ensure that the NUnit Test Adapter is enabled.
<h3>Usage</h3>
<p>In preparation for using the test adapter, make sure that the Unit
Test Explorer is shown in your window. If you don't see it, use
the menu ( <b>Unit Test | Windows | Unit Test Explorer</b> ) to show it and position
the window where you would like it within Visual Studio.
<div class="screenshot-left">
<?php echo nunit_doc_img( "nunitTestAdapter.png" ) ?>
</div>
<p>When you initially open a solution, no tests will be displayed.
After compiling the assemblies in the solution, Visual Studio will
interact with the NUnit Test Adapter to discover tests and a list
of them will be shown in the Unit Test Explorer.
<p>Click on <b>Run All Tests</b> in the Unit Test Explorer to run
all the tests. You may also select one or more tests in the list and
run them by right-clicking and using the context menu.
<p>The context menu also contains entries for debugging tests and for
navigating to the source code of a test.
<h3>Known Problems</h3>
<ol>
<li><p>There is no test status corresponding to NUnit's <b>Inconclusive</b>
result, so tests with this result are reported as <b>Not Run</b>.
<li><p>Test cases appear in a flat list, without any grouping by fixture or
namespace. This can make it hard to select a group of related tests
to be run. It is, however, relatively easy to rerun all failing tests.
<li><p>Theories are reported as individual cases, rather as a single unit.
<li><p>Startup performance is now improved as compared to the developer
preview, but is still intermittently slow.
</ol>
<h3>Reporting Problems</h3>
<p>Bugs should be reported using the separate test adapter
<a href="http://bugs.launchpad.net/nunit-vs-adapter">bug tracker</a> on Launchpad.

28
docs/2.6/vsTestAdapterLicense.html
Просмотреть файл

@ -1,28 +0,0 @@
<h2>License - NUnit Test Adapter for Visual Studio 11</h2>
<p><b>Copyright &copy; 2012 Charlie Poole</b>
<p>Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
<p>The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
<p>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
<h4>Notice</h4>
<p>NUnit 2.6 assemblies distributed with this adapter are subject to the
<?php echo nunit_doc_link("license", "NUnit license") ?>.