Skip to content

jcansdale/TestDriven.Net-Issues

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

75 Commits
ExampleProjects
ExampleProjects
 
 
images
images
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 

Repository files navigation

TestDriven.NET

Installers

You now have a choice of installers for TestDriven.NET

TestDriven VSIX

  • Works with Visual Studio 2015 and later (up to 2019 at time of writing)
  • Supports Nunit 3.x, xUnit, MSTest (not from NuGet) and Ad hoc tests
  • Auto updates itself

Download from Visual Studio Marketplace

TestDriven MSI

  • Works with Visual Studio 2010-2017
  • Supports Nunit 2.2, 2.4, 2.5, 2.6 and 3.x
  • xUnit, MSTest (not from NuGet) and Ad hoc tests

Download from the website

Notice anything strange?

Please report issues or tweet me!

Change log

5.0 RTW

Enhancements

  • #141 Works with Visual Studio 2015 to 2019
  • #106 Add support for running ad hoc test methods on .NET Core applications
  • #150 Honors the framework selection drop down (works .NET 3.5, .NET 4.x and all .NET Core versions)
  • #132 Execute ad hoc methods on VS SDK MEF components (use Test With > Ad hoc (VS SDK) on method in MEF component).

4.3 Beta

Enhancements

  • #109 Create a pure VSIX version of TestDriven.Net (download from the VSIX Gallery here)
  • #98 Allow .NET Standard ad-hoc methods to be executed using .NET Framework
  • #115 Honor default parameters when executing ad-hoc test methods
  • #107 Update to initialize TestDriven.Net asynchronously
  • #120 Add IgnorePortablePDBsInStackTraces in .config files
  • #108 Find a way to execute VS 2015 MSTest projects in VS 2017

Fixes

  • #122 Can't run tests in SDK style F# projects
  • #121 Full paths appear in SDK style project stack traces (not short project relative paths)
  • #113 Windows Defender started flagging installer
  • #110 [STAThread] async Task hangs when executed with Test With > In-Proc (VS SDK)

4.2 Beta

  • TDI105: Add support for Visual Studio 2017 Preview Editions Preview versions can be installed side by side with regular versions. Default install location is assumed.

4.1 RTM

  • TDI104: TestDriven.Net doesn't appear in Visual Studio 2017 / 15.3 devenv /updateconfiguration no longer updates Visual Studio's state on first launch. This exposed an issue with TestDriven.Net's installer.

4.1 Alpha

  • TDI90: Add 'Test With > In Proc (VS SDK)' for spelunking Visual Studio services and MEF exports Target methods can define any number of service interfaces and MEF [Import/ImportMany] parameters. More information here.

4.0 RTM

  • TDI88: Please re-introduce "Navigate to test or code" Add a keyboard shortcut to the 'TestDriven.NET.GoToTestOrCode' command to execute the 'Go To Code/Test' functionality (it's no longer on the code context menu).

  • TDI92: Remove support for legacy project.json/.NET Core projects .NET Core isn't currently supported. I'll revisit this when .NET Core 2.0 is released.

4.0 Beta 3

  • TDI76: Add support for Visual Studio 2017 RC TestDriven.Net will be installed for Visual Studio 2017 RC (Community, Professional and Enterprise in their default locations).

  • TDI77: Setup prompts to download .NET 3.5 on Windows 10 Installer (setup.exe) is now built using .NET 4.0 so that is can be installed on a clean installation without .NET 2.0/3.5. Also made NCoverExplorer default to using .NET 4.0.

  • TDI80: TestDriven.Net doesn't work on a 32-bit OS in Visual Studio 2015+ Fixed issue where TestDriven.Net couldn't find its home directory when running on a 32-bit version of Windows.

  • TDI83: Test With > NCover doesn't work when .NET 2.0/3.5 isn't installed Allow NCover/NCoverExplorer to run when just .NET 4.x is installed.

  • TDI72: Can you put the .csproj context menu buttons back below "build" like in VS2012? Project context menu buttons are now placed in consistent locations.

  • TDI65: Update for NUnit 3.5 Update installer to include latest version of NUnit.

  • TDI71: Test With > NUnit not working in 4.0 Beta 2 Restore option to test using the old NUnit 2.5.10 GUI from project context menu.

4.0 Beta 2

  • TDI59: Add support for running "Ad hoc" async methods Async methods can be targeted directly and the "Ad hoc" runner will wait for them to complete (the async method mustn't return void).

  • TDI60: Develop library for testing classes that call static methods This version of TestDriven.Net was tested using StaticMocks, a helper library for mocking static methods. If you're interested, you can find it here.

  • TDI54: Label text sent to console when running multiple tests When running all tests in a project/solution, any console/trace output will be labeled with the name of the test that output it.

  • TDI63: Testing .NET Core project might fail with: "MyTests.exe isn't a .NET assembly" When a "runtimes" element was defined in a .NET Core project, it was attempting to execute the native EXE shim rather than the target assembly DLL.

  • TDI17: Automatically pass DTE object to "Ad hoc" test methods that take DTE as a parameter The 'Test With > In-Proc' command will pass the current DTE (Visual Studio) object to "Ad hoc" test methods that take DTE (or DTE2) as a parameter.

  • TDI52: Add support for new VSTestHost when executing 'Test With > In-Proc' VisualStudio TestHost project can be used for writing Visual Studio integration tests. As a quick way to prototype a test, the 'Test With > In-Proc' command will populate initialize the VSTestContext class, giving easy to the current ServiceProvider and DTE objects. Click on this issue for an example.

  • TDI29: Run using .NET Framework (and "quirks mode") that project.json is targeting When running tests using the 'dotnet test' based runners, run using the exact .NET Framework version and "quirks mode" they were compiled for.

  • TDI50: CurrentDirectory not set for dotnet-test based test runners The current directory wasn't being set when executing using a 'dotnet test' based test runner. It is now being set to the output directory (consistent with other TestDriven.Net runners).

  • TDI53: When running project.json tests, always target tests specified by testRunner When targeting a 'project.json' based project, run using the "Ad hoc" runner if a non-test method is targeted (no test attribute), otherwise only consider the testRunner specified in 'project.json'.

  • TDI44: Remove Go To Code/Test command This command was rarely being used and taking up valuable space on the context menu.

4.0 Beta

  • TDI#21: Add 'Test With > .NET' and 'Test With > .NET Core' commands

  • TDI#40: Add support for .NET Framework / .xproj based projects that use ITestRunner interface

  • TDI#36: Add support for App.config when running .xproj / .NET Framework tests

  • TDI#14: Add support for running "Ad hoc" test methods in .NET Core Class Library projects

  • TDI#27: Add support for targeting .NET Framework .xproj 'Library' projects

  • TDI#23: TestDriven.Net tries to run tests in .NET Core projects that don't contain tests

  • TDI#18: .NET Core test runner should honor the NUGET_PACKAGES environment variable

  • TDI#7: Can't resolve some assemblies when targeting .NET Core 'Class Library' projects

  • TDI#33: Skip .xproj / project.json style projects that don't contain any tests

  • TDI#34: Can't find .xproj assembly when project name is different to folder name

  • TDI#37: Look for DLLs in RID directory, not just EXEs

4.0 Alpha

TDI#3: Add support for .NET Core testing

.NET Core assemblies can now be targeted using Visual Studio 2015 Update 3 with .NET Core 1.0

TD#7: Add support for Visual Studio "15" preview (full and lightweight installs)

If you add or remove features using the lightweight installer, you will need to reinstall TestDriven.Net 4.

TDI#14: Add support for running "Ad hoc" test methods in .NET Core Console and Class Library projects

Any .NET Core method or property can be executed using the 'Run Test(s)' command. Any returned value or object will be expanded on the output window.

TDI#10: Add support for .NET Core debugging

.NET Core projects can be debugged using the Test With > Debugger' command.

TDI#6: Add support for running NUnit tests using .NET Core

Install the 'dotnet-test-nunit' and 'NUnit' packages from NuGet to run NUnit .NET core tests.

TDI#5: Add support for running xUnit tests using .NET Core

Install the 'dotnet-test-xunit' and 'xUnit' packages from NuGet to run xUnit .NET core tests.

TDI#8: Allow .NET Core test runner projects to test themselves

The tests for .NET Core xUnit and NUnit test runner projects can now be executed using TestDriven.Net (the test runner is used to run tests on itself).

TDI#11: Can't target tests in .NET Core nested types

The tests in nested types will now be executed when an outer type is targeted (xUnit and NUnit).

TDI#5: Clean up output when an xUnit test fails

Cleaned up the reporting of failed tests and changed to use relative paths in stack frames.

Please add a feature request here if there is another test runner you would like to see supported.

3.10 RTM

TDI#28: Can't evaluate "Ad hoc" properties in NUnit test projects

Attempting to target a property in NUnit test projects would result in an exception rathere than property being evaluated.

TDI#22: 'Test With > Performance' not working on Visual Studio 2013 Premium

Symbols appeared not to be found when attempting to profile a test in Visual Studio 2013 Premium.

NTA#12: Add support for running nested classes when a parent class is targeted (NUnit 3.x)

Some people like to use nested classes to arrange their tests.

NTA#5: Add support for executing tests in concrete sub-classes when abstract class is targeted (NUnit 3.x)

Targeting abstract test fixtures in now supported.

NTA#6: Add support for targeting generic test fixtures (NUnit 3.x)

Generix fixtures and their contained methods can now be targeted.

NTA#