TestCentric .NET 8.0 Pluggable Agent
Now that the .NET 8.0 preview is out, many folks will want to experiment with it and possibly run tests under the TestCentric GUI. A newly released extension, the .NET 8.0 Pluggable Agent, makes this possible.
Note: The code for this article was developed under Visual Studio .NET 2002.
NUnit Engine Version Conflicts in Visual Studio
There have been some issues filed recently about exceptions being thrown when running NUnit tests under the VS test window. In many cases, they result in trying to install two different versions of the NUnit Engine into the same project directory. I'll try to explain how the problem arises and what to do about it. The table at the end of this post will also be useful to anyone wanting to know which version of the engine is being used by the adapter version they have installed.
Moving to TestCentric 2.0
NUnit 2.0 through 2.7 was delivered as an all-inclusive package: test framework, console runner and GUI runner. With NUnit 3 that changed. The framework and console runner became separate packages and the GUI was no longer developed.
The Ebb and Flow of Open Source
I'm in the process of moving many of my old posts to a new website - this one - and that involves thinking about some things I have not thought of in years.
Is XP Unsuitable for a Diverse Team?
A post on Twitter claimed that Agile won't work for a heterogeneous team because it's practices were developed by a "bunch of white dudes." While that isn't something I want to believe, the comments indicated that many folks did believe it. When a large body of opinion contradicts my assumptions, I like to pause for thought.
What's With NUnit 2.6.5?
Some folks have expressed surprise at my release of NUnit 2.6.5. Their surprise is no surprise, given that the NUnit framework is now at version 3.10.1!
Microtests and Test Frameworks
I'm a big fan of microtests - both the term and the thing itself. My friend Hill coined the term quite a while back and I felt it completely solved the problem of ambiguity we agile folks were having when we talked about unit tests in front of people who understood the term in the way it was used 30 or more years ago.
Future of NUnit
A while back I began to have some concern about the future of NUnit. I was entering my 70s and I knew I wanted to spend more time on other things. NUnit had been very much my project for a few years and I didn't want it to die when I was no longer maintaining it.
An Engine Extension for Running Failed Tests
In a recent online discussion, one of our users talked about needing to re-run the NUnit console runner, executing just the failed tests from the previous run. This isn't a feature in NUnit but it could be useful to some people. So... can we do this by creating an Engine Extension? Let's give it a try!