nunit3-vs-adapter

nunit3-vs-adapter copied to clipboard

Theory (random/dynamic data driven) tests always inconclusive with AutoFixture and NSubstitute

8

Hi, I have a similar situation to #97, though probably more complex. Using AutoFixture and NSubstitute, I can declare tests as such: ``` [Theory, AutoSubstituteData] public void Test_Mixed(int version, string...

jocutajar

Regression in handling C++ files

5

I recently upgraded from 3.4.1 to 3.6.0 and now my native tests are failing in VSTS. Previously the adapter ignored things it couldn't handle, now it raises an error Here's...

phatcher

How to ignore .NET Core test assemblies in the same solution

4

Running NUnit tests in "classic" (MSBuild/.csproj-based) .NET test projects using NUnit3TestAdapter works just fine. Running NUnit tests in .NET Core (dotnet/.xproj-based) test projects using dotnet-test-unit works just fine. Having both...

msitms

@CharliePoole commented on [Thu Oct 17 2013](https://github.com/nunit/nunit-vs-adapter/issues/11) We are having problem with the test adapter in our TFS build environment. Here are the versions used: - NUnit version 2.6.2 -...

CharliePoole

@lawrencecraft commented on [Wed Mar 25 2015](https://github.com/nunit/nunit-vs-adapter/issues/67) Output from F#'s printfn is displayed with a newline after every character. See screenshots attached. Sample code: ``` module tests open NUnit.Framework []...

CharliePoole

@CharliePoole commented on [Thu Oct 17 2013](https://github.com/nunit/nunit-vs-adapter/issues/10) Hello, I've been trying to enable a good size project to use the NUnit Test Adapter under TFS Build (0.96). Some of the...

CharliePoole

Test adapter ignores fixtures that failed to be built

4

If an `ITestBuilder` for a given test method throws an exception, all tests in the same fixture disappear from the Visual Studio Test Explorer. There is no warning or error...

yaakov-h

Return better information about assembly load failures

1

A non-runnable test suite is returned when an assembly cannot be loaded for one reason or another. The only information that distinguishes various reasons for an invalid suite is the...

CharliePoole

Overloaded parametrized test methods point to non-overloaded version

1

If there are multiple overloads, like Foo(), Foo(string s), the Test Explorer will navigate only to the source of Foo() from both. See #104 for details

OsirisTerje

[Enhancement] Report non-runnable tests during test discovery

4

Currently to discover that test case source throws exception for some reason, user needs to run test. It would be nice, if adapter could report error message to Tests output...

MaceWindu