NCoverExplorer… v1.4.0Syndicated from Kiwidude’s Geek Spot I’ve had this "quietly
October 30, 2008 – 10:00 pmSyndicated from Kiwidude’s Geek Spot
I’ve had this "quietly available" on the download page for a few weeks to gain feedback on any issues and with no known issues outstanding it seems appropriate to more publicly announce it.
A big change in NCoverExplorer 1.4.0 is that it is no longer published under the GPL license. I made this change for a number of reasons; amongst which was the concern that a number of companies have of deploying GPL based tools into their development process. This roadblock has been removed and should no longer prevent your companies from using this toolset.
My original choice of GPL was based on using the ICSharpCode 1.x texteditor control. I have now dropped that component in favour of using the superior (but commercial) Actipro SyntaxEditor control instead. The improvements are not only in stability and features but also visual as you can see below in the code highlighting screenshot. A splitter window is available as also shown.
So why should you upgrade to NCoverExplorer 1.4?
This release is less about adding new features (although there are some to be found) and more about stabilisation for the future. The core model code has been rewritten and better tested. There have been countless code coverage corner cases (say that five times in a row!) arise that should be better catered for. Better performance for .NET 2.0 users, lower resource usage, better error handling and some minor gui quirks addressed.
Some of the "internal" changes have spilled over externally. For instance the configuration file format used by NCoverExplorer.Console with /c has changed to support new features, although I have retained legacy compatibility for those who choose not to upgrade their build scripts immediately.
What about the new features? Well, the ones I did squeeze in were…
- Support for the //pm (profiling a process by name) argument in NCover 1.5.8;
- Copy command in the source code text area via right-click;
- Print preview command in the File menu;
- /fc argument for NCoverExplorer.Console to fail a build if the combined total coverage of all assemblies does not meet the minimum specified. This was the original behaviour of the /f command before it was changed to fail if any individual assembly does not meet the minimum;
- Coverage exclusions now support the ‘?’ wildcard and multiple ‘*’ wildcards within the expression.
- Report xml contains a "totalSeqPoints" attribute as requested for developers writing alternate xsl reports that need to calculate the excluded code at each level;
- Update the NAnt/MSBuild task dlls to support the latest changes;
- Redesigned the options dialog as shown below;
VBUG Newcastle: Introducing OpenXML with Craig Murphy ? Wednesday 29th October 2008
Many thanks to Andy Westgarth for organising a very interesting talk on OpenXML, given by Craig Murphy yesterday. Craig gave an excellent introduction to Open XML file formats in general and specifically the Open XML Format SDK 2.0.I've been working recently on a project migrating SharePoint 200
The Many Flavors of Testing (An Excerpt from Software Conflict 2.0) By Robert L. Glass
Once we realize that we are committed to a future full of testing, it is worth exploring what testing really means. I would assert that there are several flavors of testing, and that all too often when we speak of testing we consider far too few of those flavors. An excerpt from Software Conflict 2.0.
Click here for the full article.
TestDriven.Net 2.11: Parameterized NUnit Tests
TestDriven.Net has always supported parameterized test methods when used with the MbUnit testing framework. When using MbUnit, it is common for a single test method to execute multiple tests with different parameter inputs. The most famous of these test types is the MbUnit RowTest.
Until now there has been little reason to add support for executing parameterized tests using NUnit (historically NUnit has only supported parameterless test methods). However Andreas Schlapsi has recently written an implementation of MbUnit’s RowTest using NUnit 2.4’s Addin extensibility mechanism.
I’ve updated TestDriven.Net 2.11 to better support NUnit add-ins and enable the targeting of RowTests and other parameterized test types. This version also includes a workaround for a log4net related issue that was causing a noticeable delay when launching the NUnit 2.4 GUI. You can find the release notes for TestDriven.Net 2.11 here.
To install the RowTest Extension for NUnit you will need to do the following:
- Download and install TestDriven.Net 2.11.
- Download the RowTest Extension for NUnit 2.4.5 (Binary).
- Create a directory called ‘addins’ in ‘%ProgramFiles%\TestDriven.NET 2.0\NUnit\2.4′.
- Copy the ‘NUnitExtension.RowTest.AddIn.dll’ file into the ‘addins’ directory (don’t put any non-assembly files there).
- Add a reference to ‘NUnitExtension.RowTest.dll’ from your NUnit test project.
You can then start writing and executing MbUnit style RowTests inside your NUnit projects! You can find Peli’s original RowTest example here.
To view your RowTests inside the NUnit GUI you will need to use ‘Test With > NUnit 2.4′. You will find this option on the ‘Solution Explorer’ project context menu.
Thanks to Wayne Brantley for letting me know about the RowTest Extension for NUnit.
Offline Silverlight Applications
I think Scott Guthrie first mentioned the ability to take Silverlight applications offline in his keynote on Tuesday. It raised a few eyebrows but few details were forthcoming on how exactly this was accomplished. The answer is that you can create Silverlight applications that run inside Live Mesh
You must be logged in to post a comment.