nunit/nunit3-vs-adapter

NUnit 3 VS Test Adapter

The NUnit 3 Test Adapter runs NUnit 3

NUnit 3 VS Test Adapter

NUnit 3 VS Test Adapter

The NUnit 3 Test Adapter runs NUnit 3.x tests in Visual Studio 2012 and newer.

This adapter works with NUnit 3.0 and higher only. Use the NUnit 2 Adapter to run NUnit 2.x tests.

You can download the latest release version

or the latest pre-release version

Builds on master

Support

Ask support questions or raise an issue

Documentation

The NUnit3TestAdapter wiki is the best place to start.

Also check the release notes.

License

The NUnit 3 Test Adapter is Open Source software released under the .

Developing

Visual Studio 2019 is the minimum required version to build the adapter.

Use .\build -t test at the command line to build and run complete tests.

To create a package use .\build -t package

To run and debug tests on .NET Framework, load DisableAppDomain.runsettings.

From Visual Studio 2019 version 16.2 preview 4 it is possible to run tests against a selected target framework in the test project, so one can use this to run .NET Core tests. An alternative approach is to make use of the command line. If you need to frequently debug into .NET Core tests, you can temporarily switch the order of the <TargetFrameworks> in NUnit.TestAdapter.Tests.csproj.

The mock-assembly tests are not for direct running.

See https://github.com/nunit/docs/wiki/Packaging-the-V3-Adapter for more details.

Debugger source-stepping

The NuGet package and the VSIX contain source-linked PDBs for the adapter. If you’re in the middle of a debugging session and realize you’d like to be able to step into NUnit adapter code, set breakpoints and watch variables, follow these steps.

Announcement

  • From version 3.9 the NUnit3TestAdapter will stop supporting Visual Studio 2012 RTM (!), note only RTM, the later updates will still be supported fully. If you're using VS 2012 and want to update NUnit3TestAdapter, please update your Visual Studio RTM to any of the subsequent updates (Update 1-5)
  • From version 3.16 the NUnit3TestAdapter will stop supporting .net core 1
Issues

Quick list of the latest Issues we found

varnk

varnk

reproNeeded
Icon For Comments2
  • NUnit 3.13.3, NUnit3TestAdapter 4.2.1
  • Visual Studio Enterprise 2017 15.9.49
  • .Net Framework 4.6.1

Steps to reproduce:

  1. Startup Visual Studio
  2. Load my test solution.
  3. Right-click in Test Explorer or right-click on the test method in the code.
  4. Select Debug Test

At this time, the wrong test will run. Usually it is the first test that is found in the test DLL.

Sometimes if I do a rebuild of the solution, then attempt to debug the selected test again, the correct test will run. This does not always work and may require one or more attempts before the selected test is actually run.

varnk

varnk

is:enhancement
Icon For Comments2
  • NUnit 3.13.3
  • NUnit3TestAdapter 4.2.1
  • Visual Studio 2017 Pro 15.9.49
  • .NET Framework 4.6.1

When using a .runsettings file and enabling TRX logging, the TRX logs are written relative to the solution dir of the VS project. However, the NUnit XML output is written relative to the NUnit WorkingDir folder. There seems to be no way to have the test result output files go to the same folder with the way the .runsettings file is interpreted by the plug-in.

RedHeadIvan

RedHeadIvan

Investigate
Icon For Comments4

Setup:

  • NUnit 3.13.3
  • NUnit3TeasAdapter 4.2.1
  • VS2022
  • .NET5

Wrote single test for module that runs with multiple threads and writes logs by NLog. Runed this test, all necessary logs are present in test journal. Then I splited it to OneTimeSetUp and Test to write another test with similar logic. After that test journal contains only logs writed by Test method thread. Missing output from HostRepresentative_CorrectionReady and other threads that triggers by ValueChanged method.

loop-evgeny

loop-evgeny

Icon For Comments0

NUnit 3.13.2, NUnit3TestAdapter 4.2.1, Visual Studio 2022 Pro, 17.0.5, .NET Core 3.1

I have a custom IFixtureBuilder that generates tests with variable names. I noticed that under the VS test runner any name change is not picked up the first time, but only on the subsequent run. For test names that always change this means they never get run at all! All tests run every time under dotnet test or the ReSharper test runner, however.

To reproduce open NUnitDiscoveryNameChange.zip in VS 2022 and select Test, Run All Tests. The tests output window shows:

Run it again and, depending on your luck, you might have the same output or "Test with random zero or one" may also run:

loop-evgeny

loop-evgeny

is:bug
Icon For Comments17

When reporting a bug, please provide the following information to speed up triage:

  • NUnit 3.13.2, NUnit3TestAdapter 4.1.0 (also happens on 4.2.0-beta.4)
  • Visual Studio 2019 (16.11.8) and 2022 (17.0.4)
  • .NET Core 3.1

Repro: NunitFSharpTestCaseSource.zip

I have a C# test project with a TestCaseSource that uses an F# type (discriminated union). When I try to run all tests using the VS test runner no tests get run and the Tests output window shows

I can run the test using dotnet test from the command line, however.

This looks like bug #691 which was closed a while ago.

plainionist

plainionist

is:bug
Icon For Comments28

Running "dotnet test" with a test filter for a test case with spaces the following exception occurs:

dotnet test --settings ../../../build/.runsettings --no-build --logger "trx;LogFileName=C:\Temp\0.trx" --filter "FullyQualifiedName="BackLook.Apps.WorkInProgress.Specs.Computing work in progress Project.No Workpackages exist"" --no-build

Test run for C:\ws\BackLook\system\App.WorkInProgress\BackLook.Apps.WorkInProgress.Specs\bin\Debug\net48\BackLook.Apps.WorkInProgress.Specs.dll (.NETFramework,Version=v4.8) Microsoft (R) Test Execution Command Line Tool Version 16.10.0 Copyright (c) Microsoft Corporation. All rights reserved.

Starting test execution, please wait... A total of 1 test files matched the specified pattern. An exception occurred while invoking executor '#404': Unexpected Word 'work' at position 64 in selection expression. Stack trace: at NUnit.VisualStudio.TestAdapter.TestFilterConverter.TestFilterParser.Expect(Token[] valid) in D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\TestFilterConverter\TestFilterParser.cs:line 252 at NUnit.VisualStudio.TestAdapter.TestFilterConverter.TestFilterParser.Parse(String input) in D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\TestFilterConverter\TestFilterParser.cs:line 66 at NUnit.VisualStudio.TestAdapter.NUnitTestFilterBuilder.ConvertVsTestFilterToNUnitFilter(IVsTestFilter vsFilter) in D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\NUnitTestFilterBuilder.cs:line 72 at NUnit.VisualStudio.TestAdapter.NUnit3TestExecutor.RunTests(IEnumerable1 sources, IRunContext runContext, IFrameworkHandle frameworkHandle) in D:\repos\NUnit\nunit3-vs-adapter\src\NUnitTestAdapter\NUnit3TestExecutor.cs:line 116 at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Execution.RunTestsWithSources.InvokeExecutor(LazyExtension2 executor, Tuple2 executorUriExtensionTuple, RunContext runContext, IFrameworkHandle frameworkHandle) at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Execution.BaseRunTests.<>c__DisplayClass48_0.<RunTestInternalWithExecutors>b__0() at Microsoft.VisualStudio.TestPlatform.PlatformAbstractions.PlatformThread.<>c__DisplayClass0_0.<Run>b__0() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.VisualStudio.TestPlatform.PlatformAbstractions.PlatformThread.Run(Action action, PlatformApartmentState apartmentState, Boolean waitForCompletion) at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Execution.BaseRunTests.TryToRunInSTAThread(Action action, Boolean waitForCompletion) at Microsoft.VisualStudio.TestPlatform.CrossPlatEngine.Execution.BaseRunTests.RunTestInternalWithExecutors(IEnumerable1 executorUriExtensionMap, Int64 totalTests)

according to https://docs.microsoft.com/de-de/dotnet/core/testing/selective-unit-tests?pivots=mstest spaces and special characters can be encoded using "url style encoding" but that causes the same exception.

example: --filter "FullyQualifiedName=BackLook.Apps.WorkInProgress.Specs.Computing%20work%20in%20progress%20Project.No%20Workpackages%20exist"

i am using

<PackageReference Include="nunit" Version="3.12.0" /> <PackageReference Include="NUnit3TestAdapter" Version="4.0.0" /> <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.3.0" />

and "dotnet cli" version 5.0.301

bernd5

bernd5

is:question
Icon For Comments3

Hello, I'd like to adjust the "Class" or some other column in VS Test Explorer after test execution with a simple text: grafik

I would like to see there something like the exception class (FeatureXYZNotImplementedException). The text should be adjustable.

My tests are based on [TestCaseSource(nameof(TestFiles))].

The main reason for this is that I want to get more outcome states: not just "fail" and "pass".

SabotageAndi

SabotageAndi

confirm
Icon For Comments6

When reporting a bug, please provide the following information to speed up triage:

  • NUnit and NUnit3TestAdapter versions: NUnit: 3.12 NUnit3TestAdapter: 3.15.1
  • Visual Studio edition and full version number (see Help About) VS 2019 Enterprise Version 16.8.1
  • A short repro, preferably attached or pointing to a git repo or gist https://github.com/SabotageAndi/NUnitRetry2213
  • What .net platform and version is being targeted .NET Core 3.1
  • If TFS/VSTS issue, what version, hosted, on-premises, and what build task you see this in Azure DevOps/ VSTest Task V2

The Azure DevOps VSTest task has the functionality to rerun failed tests. It looks like it doesn't work when you are using TestCaseAttributes and have spaces or ampersands (&) in the parameters.

Error:

Code:

The code is generated by SpecFlow, but I think we are generating the code correctly. We could escape the string in SpecFlow when we create the code, but there would nowhere be a normalization of it.

Repro project: https://github.com/SabotageAndi/NUnitRetry2213 GitHub Issue at SpecFlow: https://github.com/SpecFlowOSS/SpecFlow/issues/2213

For me, it looks like there is some escaping missing in the test adapter full qualified name generation for spaces.

denvermadsen

denvermadsen

is:bug
Icon For Comments2

Environment:

  • NUnit v3.12.0
  • NUnit3TestAdapter v3.17.0
  • Microsoft.NET.Test.Sdk v16.7.1
  • Visual Studio Community 2019 16.7.2
  • .NET Core 3.1

Summary: Unit tests parameterized with an IEnumerable of tuples (via TestCaseSource) is not run with Test Explorer's Run All button.

Expected Behavior: All test cases are enumerated in Test Explorer with Fail or Pass statuses upon pressing Run All. In sample provided, it is expected that the test case will fail with a red X badge in Test Explorer.

Current Behavior: Test Cases are not run, status for tests are unfilled blue badges. Outputs the following error: ========== Test discovery finished: 1 Tests found in 686 ms ========== ---------- Starting test run ---------- NUnit Adapter 3.17.0.0: Test execution started An exception occurred while invoking executor '#404': Incorrect format for TestCaseFilter Error: Missing '('. Specify the correct format and try again. Note that the incorrect format can lead to no test getting executed. ========== Test run finished: 0 Tests run in 460.3 ms (0 Passed, 0 Failed, 0 Skipped) ==========

Additional Notes: A workaround is observed: test runs if using TestCaseData.SetArgDisplayNames()

Repro steps: Either: open solution in Sample.zip and run tests in Test Explorer OR:

  1. Create new .NET Core 3.1 console project
  2. Add NUnit Test project to solution (w/ Nuget packages Microsoft.NET.Test.Sdk, NUnit and NUnit3TestAdapter )
  3. Add unit test method with parameter of type IEnumerable<(object, object)> and method attribute [TestCaseSource(...)]
  4. For target class of TestCaseSource, implement IEnumerable interface and return a test case with tuple, e.g. yield return new TestCaseData(new[] {(new object(), new object())});
  5. Open Visual Studio Test Explorer and press Run All.
  6. Observe blue unfilled status icons of tests, error in Output/Tests image image
LiohAu

LiohAu

VS Issue
Icon For Comments5

I don’t know if I am facing a bug or not, but the parameters of my .runsettings file are not accessible from the TestContext.Parameters variable when I run a test.

I am using VS Mac and I did not find a window to indicate the .runsettings to use, so I tried to add thoses lines of code to my .csproj, but that still does not work :

$(MSBuildProjectDirectory).runsettings

I am using NUnit with SPecFlow (if that matters).

Thanks for your help.

mzboray

mzboray

is:enhancement
Icon For Comments9

I recently happened to need to use xUnit.net for a test project because it had one key feature that seemed to be missing from NUnit. This is an option to not create any appdomain's when running tests. xUnit.net supports this as part of its configuration (see appDomain=denied). I looked at several NUnit issues and Stack Overflow questions but could not find an exact equivalent to this option, at least for the VS adapter. I believe the NUnit console has its own runner options for this but haven't looked into it too closely.

There is the DisableAppDomain of runsettings however I could not get this to work for my use case. I believe NUnit and xUnit behave the same with this setting but it still seems to create an appdomain. (xUnit does not work as desired for me with this setting.)

I realize there might be some limitations when you do this, and I am willing to deal with them as long as this option exists. For example, even with the xUnit.net option the test author needs to take over loading any dependencies with AppDomain.AssemblyResolve since the primary appdomain is the startup directory of the testhost process.

For more specifics about my use case, I was trying to write some unit tests involving the CefSharp library, which has several strict requirements: must be initialized and shutdown in the same thread, can only be initialized in the primary/default appdomain. Testing this code with NUnit with Visual Studio integration wasn't possible. I suppose I could have removed the VS adapter and tried to run these tests with the console runner, but that was too much of a hassle to deal with for a large project, especially if it meant replumbing our test pipeline in Azure DevOps.

wlf84k

wlf84k

is:bug
Icon For Comments9

Setup:

  • NUnit 3 Test Adapter 3.17.0 (tried both VSIX and nuget versions)
  • VS 2019 Professional 16.6.3
  • NUnit 3.11.0
  • Test project is .NET Framework 4.7.2 x86, dependencies might be same or .NET Standard and AnyCPU

Issue:

Test project contains 3000+ tests, in Test Explorer they are categorized and grouped so that the tree of categories/tests has multiple levels. All tests are discovered correctly. All tests can be run separately and they pass. It is also possible to run a group of tests but only if it doesn't contain a sub-group.

If group of groups of tests is run then nothing is executed and each test is marked as Not Run with a blueish exclamation mark icon. No additional information or error is provided

Some groups always work and some always not work (within the same test assembly/project)

This worked fine with VS 2017 15.9.23 and NUnit 3 Test Adapter 3.9.0

appel1

appel1

is:bug
Icon For Comments2
  • NUnit and NUnit3TestAdapter versions <PackageReference Include="NUnit3TestAdapter" Version="3.16.1" /> <PackageReference Include="NUnit" Version="3.12.0" />

  • Visual Studio edition and full version number (see Help About) Microsoft Visual Studio Professional 2019 Version 16.5.4

  • A short repro, preferably attached or pointing to a git repo or gist https://gist.github.com/appel1/579d8a44a9768e9e6e5cf93c57e5d502

  • What .net platform and version is being targeted <TargetFrameworks>net452;net472</TargetFrameworks>

The test cases show up but you can't run a specific test or all tests for that test method.

They are executed though if you run the whole project or fixture. But the test explorer do not show them as completed.

goblinmaks

goblinmaks

is:bug
Icon For Comments4

"NUnit" version="3.12.0" targetFramework="net45" "NUnit.Engine.Api" version="3.11.1" targetFramework="net45" "NUnit3TestAdapter" version="3.16.1" targetFramework="net45" developmentDependency="true"

Same behavior on dotNetCore 3.1.100

Microsoft Visual Studio Community 2019 Version 16.4.6

TestFixture with TestName displayed twice in TestExplorer, but Fixture that called as class name can't be executed via TestExplorer.

image

ashishdawale20

ashishdawale20

is:bug
Icon For Comments8

Consider the below test case, the language is Icelandic.

image

The test explorer shows this test case as

image

Notice that \u0081 is being added in between two characters as a result of which when we run this test case it is not found. image

Attaching the excel sheet with the original text because I can not copy it here. When I tried copying it here it added extra square box is added in between "ÑÐ" Foreign language.xlsx

I have also tried using the culture("es-ES") but same issue.

MattKeenum

MattKeenum

is:bug
Icon For Comments11

NUnit: v3.12.0 NUnit3TestAdapter: v3.16.1 VS Edition: Professional 2019 VS Version: 16.4.4

This issue is probably related to Visual Studio rather than NUnit, but I thought you guys might have some insight.

Issue: When using SetName and creating custom test cases, the source is no longer available in the Test Explorer.

In a previous version of VS 2019, this was not the case. Test Cases created with SetName still had the original source (even when the Test Case was duplicated). This allowed the end user to double-click the custom Test Case and it would take them to the appropriate test method. In a recent update to VS 2019, the Test Explorer got an overhaul, and that is when this issue started happening.

The same issue happened In VS 2017. However, there was an extension installed and enabled by default: Dotnet Extension for Test Explorer. We could disable this extension and all of the custom test cases would then have a source attached to them. We could double-click a custom test case and it would take us to the test method. This extension is no longer showing in the Manage Extensions for VS 2019.

VS 2019 1581087780825_image001

VS 2017 1581087791493_image002

OsirisTerje

OsirisTerje

Icon For Comments4

This is extracted from Issue #301

" FransBouma commented on Aug 15, 2017 I know I'm late to the party here, but maybe this will help:

For v3, trace output isn't picked up, as I found out the hard way as well. After a day fighting with this (also on .NET core 2.0), it appears to be rather straightforward.

As NUnit stores all output send to console output with the test result, a single tracelistener is enough: Trace.Listeners.Add(new ConsoleTraceListener()); This will store any trace info resulting from a test with the test results for that test, and if you select the test in your runner, e.g. R#, it will show the output there. For .NET core 2.0, you need to use: Trace.Listeners.Add(new TextWriterTraceListener(Console.Out));

Do this one time, in the OneTimeSetUp method in your TestFixture.

It doesn't end there though :) You can then add another tracelistener and write to a file. Trace.Listeners.Add(new add that line before or after the consoletracelistener and it writes the output also to that file.

To make sure the data is written to the file, add:

[OneTimeTearDown] public void TearDown() { Trace.Flush(); }

so it's flushed at the end of the tests.

Again, it's late, you likely already have moved on but perhaps others like me who run into the problem of not having any trace output in nunit 3 can again sleep well :) (I moved to nunit3 because we too had to support netstandard2.0 so was confronted with this).

A redundant note perhaps: parallel tests likely won't work with this.

@psulek

psulek commented on Aug 31, 2017 @FransBouma I'm currently experiencing same issue. I have netcoreapp1.1, xunit. Trying your workaroud with add trace listener and flush does not help me. Resharper unit test output is still empty. Can someone point some tips redirect dotnet test command output into resharper unit test output window?

@chostelet

chostelet commented on Nov 20, 2017 • Hello,

I concurre, having the same kind of issues. Debug.Print() statements in the application are no longer being visible in the Output window. And, as suggested above, being obliged to add a [OneTimeSetup] method just to add a ' Trace.Listeners.Add(new ConsoleTraceListener());' is hardly manageable when having thousands of unit tests. And even the result (output) is no available at once for the whole tests playlist, but needs to be pickup in each test. Hard to believe. And this should be documented in the Known Problems! Regards

@CharliePoole

Member CharliePoole commented on Nov 20, 2017 Let's note we are talking about two entirely different things here. @NightOwl888 started this issue about capture of Console.WriteLine. @FransBouma and subsequent commenters have been talking about Debug and Trace output.

It might seem as if they are the same, provided you are directing your trace to the console, but it isn't. NUnit intercepts your Console writes and the original bug applies to that. NUnit does absolutely nothing with Debug and Trace output. So we may need to look at these two things separately.

@chostelet

chostelet commented on Nov 21, 2017 It looks like, the net result to the user appears to be the same => No output in a straightforward way. I understand having the capability of parallel execution can mess up the output, but this is something one should expect anyway.

@CharliePoole

Member CharliePoole commented on Nov 22, 2017 @chostelet It's definitely an issue for the user but I wanted to note that fixing the one (console output) might not necessarily fix the other (debug / Trace). It's info for whomever takes on the issue.

@chostelet

chostelet commented on Nov 22, 2017 Hi, You're right. As a temporary workaround, does solving the console output may help get the default debug/trace output? "

felipemcoelho

felipemcoelho

is:bug
Icon For Comments14
  • NUnit 3.12.0 and NUnit3TestAdapter 3.16.1, in .NET Core 2.1
  • VS Enterprise 16.4.3

In v3.16.0, grouping works as expected using "SetName" property on TestCaseData:

image

While it was working, I had this same issue as #690, so I decided to update it to v3.16.1 to see if the problem is solved. In v.3.16.1 individual tests run normally again, but grouping doesn't work anymore. Worth to mention that this was behaving like this in previous versions too, only worked like previous print in v3.16.0, leaving the original test method name with a blank run and named tests executed.

image

ovebastiansen

ovebastiansen

is:bug
Icon For Comments8

Running the code in Visual Studio works fine, Test explorer are sucsefully finding all test cases and are able to either run all or single. The problem arises either when running "dotnet test" or in Visual Studio Code with ".net Test explorer" extension. Then running with dotnet test --filter "FullyQualifiedName=TestFixtureSourceError.TestsBroken.Test1" failes with 0 Tests found.

I know there is a workaround, that in some cases work, with TestFixtureData, but why does it work in Visual Studio then? And also when using TestFixtureData everything is then broken in Visual Studio and in Visual Studio Code, the extension(that is not your concern) still can't find or start a test and not all dotnet test --filter works.

ranax404

ranax404

is:enhancement
Icon For Comments10
  • NUnit: 3.12.0, NUnit3TestAdapter: 3.15.1
  • VS2019, Version 16.3.6
  • .net: Framework v4.8

I'm logging results by using a .runsettings with the TestOutputXml node. This works well, but on every run, the last result file is overwritten. The same behaves with the ConsoleRunner and param "--result". Therefore I created a custom resultwriter (NUnit.Extension.CustomResultWriter), which creates an additional result*.xml for each test and run (added a postfix and counter). This also works well with "--result=Result.xml";format=myformat for the ConsoleRunner.

The NUnit3TestExecutor calls the default ResultWriter "nunit3". I'm looking for a way to 1.) specify my own ResultWriter, 2.) to split the testresults into single files or 3.) append a postfix to the result.xml on each run (to not overwrite the last file)

Versions

Quick list of the latest released versions

V4.2.1 - Jan 21, 2022

See release notes here

V4.2.0 - Dec 27, 2021

See release notes here

V4.1.0 - Nov 07, 2021

See release notes for details.

V4.0.0 - Jun 08, 2021

See release notes for details

V4.0.0-beta.2 - Apr 06, 2021

V3.17 - Jul 11, 2020

See the release notes for information

V4.0.0-alpha.1 - Jul 12, 2020

See release notes for details

V3.16.1 - Jan 18, 2020

Hotfix release handling failure in 3.16 to run some tests

See release notes for information

V3.16 - Jan 03, 2020

See release notes for information

V3.15.1 - Aug 30, 2019

In some cases , see #651 , tests are failing. We therefore have introduced a featureflag to turn on PreFilter, and changed behaviour so that it default is off.

V3.15 - Aug 23, 2019

See release notes for information

V3.14 - Aug 08, 2019

See release notes for information

V3.13 - Feb 21, 2019

See release notes for information

3.11.2 - Nov 22, 2018

Fix for missing testcategories in 3.11.1

3.11.1 - Nov 21, 2018

Fixes duplicate traits issue in 3.11

3.10 - Mar 07, 2018

This release of the adapter contains several bugfixes and also sourcelink so you can debug into the adapter

See the release notes for the changes.

NUnit3TestAdapter-3.10.0.vsix.nupkg.zip NUnit3TestAdapter-3.10.0.zip

3.9 - Oct 30, 2017

This release of the adapter contains performance improvements, improved diagnostics and xml dump files, bugfixes and is updated to use NUnit 3.8.1

See the release notes for the changes.

3.8 - Jul 19, 2017

This release of the adapter supports .NET Core and .NET Standard projects in Visual Studio 2017. See the release notes for other changes.

It is recommended to install the adapter from NuGet if you are testing .NET Core or .NET Standard projects. The VSIX adapter does not, and will not, support .NET Core because VSIX packages cannot target multiple platforms.

Adding this adapter and Microsoft.NET.Test.Sdk version 15.0.0 to your NUnit test projects will also enable the dotnet test command for .NET Core projects.

Any tests using the new style CSPROJ format, either .NET Core or .NET 4.x, need to add a PackageReference to the NuGet package Microsoft.NET.Test.Sdk. Your test assemblies must also be .NET Core, not .NET Standard.

.NET Core test can be run on the command line with dotnet test, for example,

Also, note that Code Coverage and Live Unit Testing does not work with .NET Core yet. They will be supported in a future version of Visual Studio, likely post 15.3.

3.8-alpha1 - May 04, 2017

This is the first release of the adapter that supports .NET Core and .NET Standard projects in Visual Studio 2017. This is an alpha release to enable NUnit users to begin moving their .NET Core projects from the project.json format to the new csproj format.

It is recommended to install the adapter from NuGet if you are testing .NET Core or .NET Standard projects. The VSIX adapter does not, and will not, support .NET Core because VSIX packages cannot target multiple platforms.

Adding this adapter and Microsoft.NET.Test.Sdk version 15.0.0 to your NUnit test projects will also enable the dotnet test command for .NET Core projects.

Any tests using the new style CSPROJ format, either .NET Core or .NET 4.x, need to add a PackageReference to the NuGet package Microsoft.NET.Test.Sdk. Your test assemblies must also be .NET Core, not .NET Standard, I don't know why.

.NET Core test can be run on the command line with dotnet test, for example,

Also, note that Code Coverage and Live Unit Testing does not work with .NET Core yet. They will be supported in a future version of Visual Studio, likely 15.2.

3.7 - Jan 26, 2017

This release of the adapter uses the NUnit 3.6 engine. It includes support for Warning test results as well as multiple Assertion failures. A number of bugs are fixed.

3.6.1 - Dec 06, 2016

This hotfix release fixes issue #260 which prevented the vsix from installing under some VS2012 and VS2013 products. It includes only the vsix and the software installed is identical to the 3.6 release. The hotfix is intended for users of VS2012 or VS2013 who have experienced problems. Users who have been able to install the 3.6 vsix without problem, do not need to install this hotfix. Users of the 3.6 nuget package should continue to use it.

3.6 - Nov 15, 2016

Adds support for Visual Studio "15"

3.5.1 - Oct 28, 2016

This release fixes some issues in the 3.5 release, including one critical bug.

3.5 - Oct 22, 2016

This release updates the adapter to use the 3.5 release of the engine and fixes a number of bugs. See the release notes for details.

3.4.1 - Aug 05, 2016

This release fixes two critical issues and migrates the build to use Cake. See Release Notes for details.

3.4 - Jul 03, 2016

This release updates the adapter to use the NUnit 3.4.1 Test Engine and fixes a number of outstanding issues. See the release notes for details.

3.2 - Jun 04, 2016

This release updates the adapter to use the NUnit 3.2.1 test engine and fixes a number of bugs. See the release notes for details.

Library Stats (Sep 15, 2022)

Subscribers: 19
Stars: 182
Forks: 99
Issues: 71

CSharpMinifier filters comments and unnecessary whitespace from valid C#

source code in order to arrive at a compressed form without changing the

CSharpMinifier filters comments and unnecessary whitespace from valid C#

CSharpFastPFOR: A C# port of the simple integer compression library JavaFastPFOR

==========================================================

CSharpFastPFOR: A C# port of the simple integer compression library JavaFastPFOR

csharp-data-visualization

I've always wanted to learn how to visualize data in C#

csharp-data-visualization

CSharpToCppTranslator

A specific translator for LinksPlatform's libraries

CSharpToCppTranslator

CSharpDecodeSdpc

This is a tool to extract image tiles from pathological whole slide images (WSIs) based on C#

CSharpDecodeSdpc

C Sharp Helper Methods

Bu bir Windows Form uygulamasıdır ve içerisinde genel olarak ERP projelerinde sıkça kullanılabilecek bazı metotları ve kullanımlarını içermektedir

C Sharp Helper Methods

CSharp-CodeSnippet

Wide variety of sample code snippets from the topics related in C#

CSharp-CodeSnippet

CSharp &quot;C#&quot; WAVE &quot;

Parses the audio data and the format chunk info from a WAVE-Format audio file &quot;

CSharp &quot;C#&quot; WAVE &quot;

CSharp_ChromaStreamApp

C# Chroma Stream App for Chroma RGB streaming

CSharp_ChromaStreamApp

CSharp-SMTP-Server

Simple (receive only) SMTP server library for C#

CSharp-SMTP-Server

CSharp To Mindustry Logic

This is a code transpiler that will transpile C# code to mlog

CSharp To Mindustry Logic