@OsirisTerje It seems that people using .NET core projects in Windows based VS or in VS Mac/MonoDevelop are all depending on VsTest. But if you are not using a .NET core based project and that NUnit is in your project, the NUnit addin in VSMac/MonoDevelop, seems to fallback to an internal runner, and I did not find yet how to provide the settings...
@LiohAu Just for others to see, MS has confirmed this doesn't yet work on VS Mac, see https://github.com/nunit/nunit3-vs-adapter/issues/778#issuecomment-679292768. They suggest a command line work around until the issue is resolved
Issue nunit/nunit3-vs-adapter#780 - reproduces on my project, going to try to reproduce on a smaller-scale project that I can share
thanks
Hello, Is there a way to load a dll that is targeting .net framework 4.7.2 into an asp.net core web application? I have the following error when exploring the nunit tests( Tests = new TestNode(TestEngineRunner.Explore(TestFilter.Empty));):
LoadPackage(testFile);
TestEngine = TestEngineActivator.CreateInstance();
TestEngineRunner = TestEngine.GetRunner(_package);
Tests = new TestNode(TestEngineRunner.Explore(TestFilter.Empty));
The error:
NUnit.Engine.NUnitEngineException: 'An exception occurred in the driver while loading tests.'
FileNotFoundException: Could not load file or assembly 'TestingFramework, Version=9.2.2.0, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
Hello, I have a weird problem with NUnit3-console. I am trying to run my tests via command line and have NUnit.Allure for reports in my code as well. When I call the command line the console runner is stuck and neither runs tests not produces any output even when --trace=Verbose is used... Any insights? (same question goes to allure gitter. I am at a total loss here)
The project is a full .Net framework one...
@ChrisMaddock thanks for the reply , you have any suggestions to workaround this issue(nunit/nunit-console#465)? maybe to create a wcf service and to consume it via asp.net core web application, or an web api/rest app ?
Ah. I found an issue in one of my test assemblies. A
StackOverflowException, so naturally the process crashes.
Yep, that's what I did (with the equivalent
process=Single). Turned out to be that I had forgotten to enable tail calls when I converted a F# project to the new project file format. The reason I did not see the problem every time was that the test causing the trouble in turn invoked FsCheck (generating random tests).
Btw, does 3.12 drop support for the legacy nunit2 format? Using
format=nunit2 I get:NUnit.Engine.NUnitEngineException : Error encountered in resolving output specification: OutputPath: ..\Tests\TestRes
ult.xml, Format: nunit2
----> System.IO.FileNotFoundException : Could not load file or assembly 'nunit.engine.api, Version=3.0.0.0, Culture
=neutral, PublicKeyToken=2638cd05610744eb' or one of its dependencies. The system cannot find the file specified.
@batzen builds of master available here: https://www.myget.org/feed/nunit/package/nuget/NUnit. Not sure on the release date sorry, might be worth asking in an issue for the right people to see.
Hello everyone. I have a rather (IMO) unusual question. I have an assembly with tests and logging with NLog. I extended NLOG to write any logs to the console output either by using TestContext or Console.WriteLine (different set of tryouts) and I was hoping to see the logs on a TeamCity build log. Alas I only see logs from one test and the rest is only assertions. Any ideas on how to overcome this? Thanks in advance
Is there a way to hide or fix this nunit warning (I have the latest one: 3.17)? or why is this triggered at the end of the running tests?
[06.10.2020 PM 06:20:33 Warning] Exception NUnit.Engine.NUnitEngineUnloadException, Exception thrown unloading tests from D:\Git\Tests\Test\bin\x86\Debug\Test.dll
[06.10.2020 PM 06:20:33 Warning] Unable to unload application domain: unload thread timed out after 30 seconds.
Application domain was unloaded before all details could be read.
[06.10.2020 PM 06:20:33 Warning] at NUnit.Engine.Services.DomainManager.DomainUnloader.Unload()
at NUnit.Engine.Runners.TestDomainRunner.UnloadPackage()
at NUnit.Engine.Runners.AbstractTestRunner.Unload()
at NUnit.Engine.Runners.MasterTestRunner.UnloadPackage()
at NUnit.Engine.Runners.MasterTestRunner.Unload()
at NUnit.VisualStudio.TestAdapter.NUnitEngine.NUnitEngineAdapter.CloseRunner()
at NUnit.VisualStudio.TestAdapter.NUnit3TestExecutor.RunAssembly(String assemblyPath, IGrouping`2 testCases, TestFilter filter)
[06.10.2020 PM 06:20:33 Informational] NUnit Adapter 3.17.0.0: Test execution complete
[06.10.2020 PM 06:20:33 Error] An exception occurred while invoking executor 'executor://nunit3testexecutor/': Exception encountered unloading application domain
Exception encountered unloading application domain: Attempted to access an unloaded appdomain. (Exception from HRESULT: 0x80131014)
Application domain was unloaded before all details could be read.
[06.10.2020 PM 06:20:33 Informational] ========== Run test finished: 1 run (0:03:11.1407897) ==========
@marius02 If you create a small repro and raise an issue at the NUnit3TestAdapter repo https://github.com/nunit/nunit3-vs-adapter it might be possible to fix. Hiding it, you can't. It is an exception, and we can't hide them . I see the exception starts down in the engine, so it can be an NUnit engine issue too, but if we start from the adapter we can take it from there. But, we do need a repro :-)
I was wondering if I could get a summary of the v4 nunit adapter and why the major version change?
Wasn't quite sure what benefits/differences it would bring over the v3 adapter
I typically try to keep my projects on the latest of each, but couldn't find much outside https://docs.nunit.org/articles/vs-test-adapter/Adapter-Release-Notes.html on the new preview adapter
Wasn't quite sure what benefits/differences it would bring over the v3 adapter
I typically try to keep my projects on the latest of each, but couldn't find much outside https://docs.nunit.org/articles/vs-test-adapter/Adapter-Release-Notes.html on the new preview adapter
@tannergooding The reason for the major version change is that the way v4 interacts with the nunit.engine has been completely rewritten. The v3 version is heavily dependent on using XML internally all over the adapter code.
In v4 this has changed to transforming the xml to an object model at the time it is loaded from the engine, and then working on the object model instead. This brings back the Explicit feature, and the intention is to pave the way for other changes we can do. Further, under discussion is a possible drop of supporting the vsix variant, and also set the minum supported framework version to 4.5. Due to the internal rewrite there might be a intermittent loss of some features, we got one in the alpha.1 version, which is fixed now for the beta, but there might me more. However, there are around 20000 downloads now, with very few issues reported, so it might be better then feared. The changes will also pave the way for a possible better handling of the FQN issues we have - which are very annoying, and which are near impossible to handle in v3. We still need some more from MS in order to do this, but v4 should then be able to handle it. When the adapter was first written back in 2011/2012 it was a much simpler "thing" than it has become over the years. At that time the XML approach was ok, but now, the code is simply too cluttered to continue.
In v4 this has changed to transforming the xml to an object model at the time it is loaded from the engine, and then working on the object model instead. This brings back the Explicit feature, and the intention is to pave the way for other changes we can do. Further, under discussion is a possible drop of supporting the vsix variant, and also set the minum supported framework version to 4.5. Due to the internal rewrite there might be a intermittent loss of some features, we got one in the alpha.1 version, which is fixed now for the beta, but there might me more. However, there are around 20000 downloads now, with very few issues reported, so it might be better then feared. The changes will also pave the way for a possible better handling of the FQN issues we have - which are very annoying, and which are near impossible to handle in v3. We still need some more from MS in order to do this, but v4 should then be able to handle it. When the adapter was first written back in 2011/2012 it was a much simpler "thing" than it has become over the years. At that time the XML approach was ok, but now, the code is simply too cluttered to continue.
@tannergooding About the benefits in v4, in addition to bringing back the Explicit feature (and better than it was before), v4 is generally faster, and will handle large amount of tests much better. Further, with an upcoming fix in NUnit itself we can skip the pre-execution discovery phase completely, thus making the adapter even faster. This will not be possible to do with the v3 code base.
@mikkelbu Wow, I missed this:
do you know if it will be a problem that our pdb files mentions unknown files (or more precisely temp-files)?
I don't know of any downside to this. It's been the norm for pdb files to not be found.
I like to use <EmbedAllSources>true</EmbedAllSources> in my Directory.Build.props though.
2 replies
---------- Starting test discovery ----------
NUnit Adapter 3.17.0.0: Test discovery starting
NUnit Adapter 3.17.0.0: Test discovery complete
NUnit Adapter 3.17.0.0: Test discovery starting
NUnit Adapter 3.17.0.0: Test discovery complete
NUnit Adapter 3.17.0.0: Test discovery starting
NUnit Adapter 3.17.0.0: Test discovery complete
No test is available in C:\Git\_GuOrg\Gu.Reactive\Gu.Wpf.Reactive\bin\Debug\net46\Gu.Wpf.Reactive.dll C:\Git\_GuOrg\Gu.Reactive\Gu.Reactive\bin\Debug\net46\Gu.Reactive.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
========== Test discovery finished: 1279 Tests found in 7,9 sec ==========
^ is confusing, it both says tests were found and not
No tests run by visual studio runner, resharper runner runs the tests like always
You cannot do it directly, but one possibility is something like
[Test]
public void Test()
{
var data = 14;
var assertions = new List<Action>
{
() => Assert.That(data, Is.EqualTo(4)),
() => Assert.That(data, Is.EqualTo(6)),
() => Assert.That(data, Is.EqualTo(8))
};
Assert.Multiple(() =>
{
foreach (var assertion in assertions)
{
assertion.Invoke();
}
});
}