单元测试工具_单元测试工具有哪些资源-CSDN文库

共4个文件

html：3个

exe：1个

TestDriven.NET

需积分: 9 61 浏览量 2007-06-22 16:26:02 上传评论收藏 2.69MB ZIP 举报

资源推荐

资源详情

资源评论

收起资源包目录

TestDriven.NET-2.0.1948_Personal.zip （4个子文件）

TestDriven.NET-2.0 Beta 2.html 4KB

TestDriven.NET-2.0.1948_Personal.exe 3.11MB

TestDriven.NET-2.0 RC1.html 3KB

TestDriven.NET-2.0 RTM.html 10KB

<html><head><title>Release Notes - TestDriven.NET: 2.0 RTM</title> <style>  </style></head><body> <div id="FogBugzReleaseNotes"> <h1>Release Notes - TestDriven.NET: 2.0 RTM</h1> <h2>772: Can't run ad-hoc tests in NUnit project</h2> <p>Stopped 'No fixture attribute on parent class' warning when executing a non-test method in NUnit test project.</p> <h2>317: Run Test(s) not working - Private NUnit fixtures</h2> <p>Warn when attempting to run a private test fixture or test. Before the test would be executed as an ad-hoc test without any setup/teardown methods being called.</p> <h2>567: Install TestDriven.NET for all users when runnign as Administrator</h2> <p>When running as user in Administrator role, install for all users rather than just current user. This fixes installing on Vista.</p> <h2>569: Ship NCover with TestDriven.NET</h2> <p>NCover is now shipped as part of the TestDriven.NET installer. NCover 1.3.3 and 1.5.6 are included. NCover 1.5 will be used if .NET 2.0 is installed (works with Visual Studio 2002, 2003 and 2005). NCover 1.3 will be used if only .NET 1.1 is installed. Thanks to Peter Waldschmidt for allowing me to ship a non-GPL version of NCover with TestDriven.NET!</p> <h2>153: Add option to build and test with .NET 1.1/MSBee when using VS2005</h2> <p>When using Visual Studio 2005 there is an option to build and run tests using .NET 1.1.</p> <h2>275: Exceptions in test fixture setup/teardown not reported</h2> <p>Output any exceptions thrown in fixture SetUp/TearDown.</p> <h2>619: Add 'Repeat Test Run' to Solution Explorer menus</h2> <p>Made all menus with unit testing functionality consistent.</p> <h2>629: Activate 'Test' pane at end of run</h2> <p>Activate the 'Test' pane at the end of a test run so test results are visible after 'Test With... Debugger'.</p> <h2>637: Output window is activated on test run in VS2003 but not VS2005</h2> <p>Always make output window visible on test run unless window is set to auto hide. Use 'Projects and Solutions\Show Output window when build starts' option if you want 'Output' window to pop up when set to auto hide.</p> <h2>647: Warn when no test runner is found to run test(s)</h2> <p>Added warning when attempting to run a fixture with attributes from an unknown/not-installed unit testing framework.</p> <h2>697: Add an easy way to switch between NCover and Team Coverage</h2> <p>Show NCover 'Coverage' and 'Team Coverage' options on the 'Test With' menus when code coverage tools are available for use.</p> <h2>701: Only show menu items for available test runners</h2> <p>Only show test runners on 'Test With' menus that are available to use use (i.e. appropriate applications are installed). For example NCover, Team Coverage, TypeMock and .NET 1.1 (MSBee) will only appear when available for use.</p> <h2>704: Enable unmanaged code debugging</h2> <p>Added support for mixed mode and unmanaged debugging. 'Test With... Debugger' will use the 'Enable unmanaged code debugging' or 'Debugger Type' settings for the test project. The C++ debugger type 'Auto'  will always default to managed.</p> <h2>705: Add (hidden) support for 'Test With... E&C'</h2> <p>To enable 'Test With... Debugger (E&C)' that works with Edit & Continue; edit the 'TestDriven.dll.config' file and uncomment <button command="DebuggerEaC" />. This test runner may 'touch' project files when used with source control (this is why it's disabled by default).</p> <h2>708: No warning when tests project has broken App.config file</h2> <p>An appropriate warning will be output when the 'App.config' file of a test project contains invalid XML.</p> <h2>716: Add Reflector to Tools menu</h2> <p>Added 'Go To Reflector' button to Tools menu. Select a solution or project in the 'Solution Explorer' and hit 'Tools\Go To Reflector' to load project assemblies into Reflector. 'Go To Reflector' can be used from many different window contexts.</p> <h2>717: Show Breakpoints Tool Window on Reflector 'Toogle Breakpoint'</h2> <p>Show breakpoints when a breakpoint is toggled from inside Reflector (right click on a method and 'Toggle Breakpoint').</p> <h2>720: Add 'Go To Reflector' option to 'Modules' window </h2> <p>One or more modules can be selected inside the debugger 'Modules' window and opened inside Reflector.</p> <h2>721: Add 'Go To Reflector' option to 'References'</h2> <p>One of more project references can be selected and opened inside Reflector.</p> <h2>724: Allow property get to method to be executed as ad-hoc test</h2> <p>Property get methods can now be executed as ad-hoc tests.</p> <h2>737: Testing a folder's worth of test fixtures</h2> <p>Run each test fixture in the folder as a separate test run rather than assuming the folder exactly corresponds to a namespace. Only the first class in each source file will be executed as a fixture.</p> <h2>661: Rename 'Test With...' to simply 'Test With'</h2> <p>Changed to conform with menu naming conventions.</p> <h2>670: Use installed NCover unless packaged version is newer</h2> <p>Give priority to installed versions of NCover that are newer than the built in version.</p> <h2>688: Add support for running NCover with TypeMock</h2> <p>Added support for testing with code coverage when TypeMock is enabled. Simply use 'Test With... Coverage' when the TypeMock add-in is enabled.</p> <h2>694: Tests not running in 64 bit mode</h2> <p>Honor 'x86', 'x64' or 'Itanium' platform setting of test project. If platform is set to 'Any CPU' then tests will default to running in 64 bit process.</p> <h2>695: Add 'Test With... TypeMock' support</h2> <p>Added option to 'Test With... TypeMock'. This allows TypeMock to only be used on tests that require it (when the TypeMock add-in is disabled). Tests that don't require TypeMock run faster when TypeMock is disabled.</p> <h2>276: Problem with 'Test With...Debugger' + SourceGear Vault in VS.NET 2005</h2> <p>Use much faster 'Test With... Debugger' functionality when running under Visual Studio 2005 that doesn't touch project files and interfere with source control.</p> <h2>590: TestDriven.NET 1.0 and TestDriven.NET 2.0 GUID/ProgID</h2> <p>Made more robust when faced with possible left over registry entries from previous installs (e.g if an uninstall was forced using msizap).</p> <h2>605: Test With Coverage fails when running as non-admin</h2> <p>'Team Coverage' test runner is only available when running as Administrator user. NCover 'Coverage' test runner will work when running as Limited User.</p> <h2>652: Go To Reflector problems (proxy config and loading service)</h2> <p>Preserve important Reflector configuration settings when using an already installed version of Reflector. Use proper download dialog

评论收藏

内容反馈