docs/articles/vs-test-adapter/AdapterV3-Release-Notes.md
This release has a series of enhancements and bugfixes. There have been two 3.17 beta releases (beta.1 and beta.2) published earlier on nuget.org. A major bugfix is that the console output now is properly appearing. There are also a series of fixes for corner cases.
StopOnError can be very useful to reduce time of long test runs that are failing.
The ability to set custom paths for the test code can be useful with data driven tests, where you want to point to the data file (and line number therein) instead of the default C# test code.
See here for all details on the settings.
dotnet testThis is the 2nd beta for 3.17, published on Nuget.
This is the first beta release published on Nuget.
It contains new features and some bugfixes.
dotnet testThis release is a hotfix release intended to fix three major issues:
Together with these, the following issues are changed:
Note that this hotfix changes some of the new defaults introduced in 3.16.0.
These can be set back using the two new runsettings
UseParentFQNForParametrizedTests and
UseNUnitIdforTestCaseId
This release has three major changes.
The support for .NET Core 1.* has been removed. This is done to open up more functionality for the later .NET Core
versions. Also, since .NET Core 1.* is no longer supported by Microsoft, we decided to remove the support too. If
you do have .NET Core 1.* solutions and can't upgrade, you should stay with the the adapter 3.15.1 or lower. The
change also means we now support dump files in .NET Core :-). It also means the total size of the package has been
reduced by around 30%.
The filter syntax issues we've had with special names and characters have been mostly solved, thanks to excellent work by John M.Wright. The filter syntax is now closer to a correct FQN (Full Qualified Name), but this might cause some issues with your own filter in some rare cases. The fix done resolves a lot of issues, all of them listed below. For a detailed explanation of what has been done, see the Pull Request #668.
You can now use the NUnit filter syntax, either from command line or through settings in the runsettings file. This was due to an idea by Michael Letterle and a subsequent implementation Pull Request #669. Michael also wrote a great blog post to explain how this works, and how he arrived at the solution. For more information see the NUnit Test Selection Language.
All the following are solved by Pull Request #668
The following are resolved (fully or partially) by Pull Request 669
This is a hotfix release due to some issues with special cases in NUnit, causing the tests to not run. The major difference is that this release makes PreFiltering which was introduced in 3.15, optional - and default off. It can be enabled by setting PreFilter to true in a runsettings file.
651 Add feature flag to enable/disable pre-filtering. This one contains the links to the issues below:
648 NUnit3TestAdapter 3.15.0 fails to run test: "NUnit failed to load" (when using NUnit framework less than version 3.11)
649 NUnit3TestAdapter 3.15 OneTimeSetUp not working anymore (When a SetupFixture is being used)
650 NUnit3TestAdapter 3.15 not running tests with custom TestCaseSource (when using SetName instead of SetArgDisplayNames)
This release is a major performance improvement release. When used from Visual Studio, and used with a selection of tests, it will significantly speed up the discovery of those. Note that discovery is also a part of the execution, so you will also see the performance improvement for execution. It will be mostly noticeable when you have a large set of tests.
This version also includes the latest version 3.10 of the NUnit.Engine.dll
This release focuses on producing NUnit test result XML which can be useful when you need reports using tools that support the NUnit format. This can be enabled using a new setting in the runsettings file.
The VSIX is also made compatible with the upcoming VS 2019. Please note support for the VSIX is being deprecated in Visual Studio, and we strongly recommend you to change your test projects to use the NuGet adapter version.
The NUnit internal properties have been "over-populating" in the Test Explorer. These are now filtered out, although you may still see these when you have Source Based Discovery (SBD) turned on (which is the default in VS). Once you have run, they will be gone. We expect this part of the issue (SBD) to be fixed in VS.
If you still want to see the properties, you can enable that again setting a runsettings property
ShowInternalProperties to true.
WorkfolderThis is a yet another hotfix release to fix the missing categories issue.
This issue was fixed, with a workaround, in 3.11 but had unforeseen consequences, and has been reopened as of this release
This probably need to be fixed in VSTest itself.
This is a hotfix release to fix the duplicated traits issue.
PR 500 NUnit3VsAdapter to support managed sources only based on RFC (Thanks to mayankbansal018 for this PR)
543 Adapter should pass Error and Progress messages to
vstest engine as well as stdOut messages (Thanks to NikolayPianikov for PR
544). Also fixes this TeamCity
issue
Mono.Cecil is now embedded with the adapter, so user dependencies are no longer overwritten.
Indentation of the test log format makes it easier to see what information belongs to which assembly.
Quiet mode added, if you don't want all the information, see Tips and Tricks.
426 Exception thrown while loading tests if In-Proc VSTest DataCollector is used (Thanks to drognanar for PR 510 )
490 Fix Causes Build Error (Somewhat Indirectly) by published pdb files from Issue 461
494 TestContext.AddTestAttachment does not work on Linux environment with specified dotnet logger (Thanks to Kira-Lappo for PR 527)
495 Category as filter not working in single agent flow in vstest task
506 Test categories aren't propagated to vstest trx logs
516 ArgumentException when whitespace sent to logger
538 NuGet Package : Add repository metadata (Thanks to MaximRouiller for PR 539)
540 Missing null check before runner dispose
Also see Release Readiness Review
Special thanks to : Joseph Musser for awesome work on this release,
and to Loren Halvorsen for the workaround for VSTest issue 261.
This version supports Visual Studio from version 2012, Update 1 and upwards, and all subsequent versions in 2013, 2015 and 2017. Visual Studio 2012 RTM is then no longer supported.
'executor://nunit3testexecutor/'vstest.console.exe /listtests[!NOTE] This was a hotfix release of the vsix package only, fixing an issue that prevented it from installing under VS2012 and 2013.
.runsettings file.This is the final production release of the 3.0 adapter. It continues to use the 3.0.1 release of the NUnit TestEngine.
The adapter now uses a .runsettings file for all optional settings. Registry entries used in the CTP releases are no
longer used.
This release continues to use the NUnit 3.0 beta-2 engine but is nevertheless able to run tests that reference NUnit 3.0 beta-3 framework.
When a debugger is attached, only a single worker thread is used to run tests.
The adapter now compensates for the fact that NUnit does not send results for tests that were skipped due to an attribute on the fixture by generating those results itself.
This release was issued to correct a problem with locking of assemblies in ctp-2.
The adapter now uses the new nunit.core.engine to load and run tests, eliminating ad-hoc code that worked directly with the framework. This will allow us to much greater flexibility in the future.
The adapter has been upgraded to use the beta-2 release of the NUnit core engine. Because the API has changed from beta-1, the adapter can only run tests built against the beta-2 release of NUnit.
vstest.executionengine.x86.exe does not terminate