Debugging the NUnit3TestAdapter – take 2
In version 4.2 of the NUnit3TestAdapter debugging has been made simpler. You can drop directly into debugging using a runsetting property. Continue Reading →
Github and Azure DevOps specialist, Visual Studio Development Technologies MVP and NUnit core team member
In version 4.2 of the NUnit3TestAdapter debugging has been made simpler. You can drop directly into debugging using a runsetting property. Continue Reading →
A test adapter sits between a TestHost and the test framework. If you use Visual Studio or dotnet, both starts up a TestHost as a seperate process. The testhost is responsible for locating the adapters, and then invoke them to run the test frameworks on the test code. Debugging the adapters is hard, because it sits between these processes, of which you have no control. Continue Reading →
The NUnit 2.X framework have been superseded by the NUnit 3 framework several years ago. Each framework “family” needs a separate adapter, one for the V2 and one for the V3. The V3 have been maintained continuously, and have 3-4 releases per year. The V2 adapter however, has not been updated since mid 2017. The Continue Reading →
NUnit as a project has a tradition of keeping backwards compatibility. It ensures that even if you stay on a earlier version of Visual Studio, .net FrameWork, or whatever it is, NUnit should continue to work even with upgrades of NUnit. So also for the NUnitAdapter. It should work on any version of Visual Studio Continue Reading →
Once upon a time it was declared that an Assert statement should have constraints given as AreEqual and AreNotEqual. Further it was declared that it should be written in the opposite way of how a developer will think, that is with the expected value first and the actual value last. Why this was made so, Continue Reading →
NUnit has a very rich and readable constraint set. Normally you don’t need to do anything. But, there are some cases where it would be nice to be able to tweak these constraints. You can always wrap them and extend them that way, but then you lose all the other good stuff, like chaining. What is Continue Reading →
Test Adapters come in two flavors, VSIX based and Nuget based. The VSIX based are installed as extensions to Visual Studio and therefore will apply to all solutions you load, The Nuget based adapter packages must be installed at least into one project in your solution and will only work for that solution. All versions Continue Reading →
I have had a need to have more easy access to information on how to do certain stuff, and have some easy access to simple code blocks, or templates, I can copy/paste. A blog post is for me somewhat more extensive, and that format was not really suited for smaller notes. So I decided to Continue Reading →
The Visual Studio Test Explorer can be a bit picky about showing tests. There are multiple reasons for why they don’t always show up when you expect them to do, and most of the cases are PEBKAC type of issues. That doesn’t mean it is easy, there are just becoming too many variations, and Visual Continue Reading →
The Visual Studio Test Explorer user interface have been nearly the same since 2012, with only a few minor updates. One thing that have annoyed a few people are how the test names are displayed. The Test Explorer have got a bit of critique on this, but it is not that hardcoded. It can be Continue Reading →
Caches On Windows:
%LocalAppData%\NuGet\Cache
%UserProfile%\.nuget\packages
To clear: nuget locals all --clear
Feed url: https://api.nuget.org/v3/index.json
VSTest
NUnitAdapter, use runsettings
From admin prompt:
Start powershell:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
https://www.microsoft.com/net/download/visual-studio-sdks
Add this tag to the initial propertygroup
AppendTargetFrameworkToOutputPath
Set value to false