Table of Contents
NUnit Extensions
Extensions are separate programs, which have been created to extend and enhance the use of NUnit. For convenience, we group them in categories, as described below.
Types of Extensions
Addins
Addins plug into the NUnit core and change how it operates. They usually provide an entirely new type of test and may even link to or emulate a different framework. Most addins also include an extension to the framework, such as a new attribute, but the key functionality is in the addin itself.
Addons
Addons build on top of the NUnit framework, or are used in conjunction with it, without requiring any “hooks” within the NUnit core itself. Some of them work with other frameworks in addition to NUnit. Generally, they are used for testing a particular type of application or for implementing a particular test-writing style.
Runners
Runners are alternative programs for running NUnit tests, available separately from the NUnit project. This includes various IDEs and addins that use NUnit as well as batch-oriented tools used for continuous integration.
Extras
Extras is a term we coined for programs used in conjunction with NUnit, which don't fit into any of the other categories. Some of them operate by processing the output of a test run. This category can also include utility programs used to create or manage tests.
Available Extensions
| Extension | Description | ↓ Type | Author |
|---|---|---|---|
| Rowtest | Allows writing mbUnit-style RowTests under NUnit | Addin | Andreas Schlapsi |
| FireBenchmarks | Performance testing addin for NUnit. | Addin | Federico Coletto |
| Common.Addin.Build | Common build script for use in building NUnit addins. | Addin | Charlie Poole |
| CSUnit Addin | Runs csUnit tests under NUnit without recompilation. | Addin | Charlie Poole |
| IterativeTest | Data-driven testing alternative. | Addin | Kelly Anderson |
| Xtunit | Rollback data changes made by a test. | Addin | Roy Osherove |
| Njasmine | A DSL for writing tests as Given/When/Then specifications, inspired by Jasmine. | Addin | Frank Schwieterman |
| ORAYLIS BI.Quality | ORAYLIS BI.Quality is a testing suite for BI solutions makes it easier to develop in an agile environment. The suite is based on NUnit and supports quite a lot of different testing methods. | Addon | Thomas Strehlow (ORAYLIS GmbH) |
| ExpressionToCode | Write assertions as C# lambda expressions; can annotate subexpressions with their runtime value if the assertion fails. Use C# as an assertion DSL. | Addon | Eamon Nerbonne |
| NBi | NBi is a add-on to NUnit for Microsoft Business Intelligence platform and Data Access. | Addon | Cédric L. Charlier |
| NUnitEx | NUnit constraint syntax based on extension methods | Addon | Fabio Maulo, Simone Busoli |
| Extension Methods For Nunit | A DSL for constraint specification | Addon | Jonathan Knezek |
| Sharp Tests Ex | NUnit constraint syntax based on extension methods | Addon | Fabio Maulo |
| Nunit-Results | Produces HTML reports from one or more NUnit test runs. | Extra | Charlie Poole |
| Nunit-summary | Produces HTML or text reports from one or more NUnit test runs. | Extra | Charlie Poole |
| Watin Test Recorder | Tool for use of WatiN with NUnit. | Extra | Daaron Dwyer, Nick Journals, James Avery |
| VisualNunit | Open Source NUnit plugin for Visual Studio 2008 and 2010 | Runner | Tommi S. E. Laukkanen |
| MSBuild-NUnit | MSBuild task to run NUnit | Runner | Rafael Teixeira & Paul Welter |
| TestDriven.Net | Zero friction unit testing extension for Visual Studio | Runner | Jamie Cansdale |
| NAnt-task | NAnt task to run NUnit | Runner | Daniel Nauck |
| NUnit Via LINQPad | Code snippet for running NUnit tests inside LINQPad. | Runner | Simone Busoli |
Adding Your Extension
To add your own extension to this list, you need to create a page in the 'extras' namespace, following the required template. Here's how:
1. Enter a URL like the following in your browser, replacing my_cool_extension with the name you want to give your page. Note that the underscores will be replaced with spaces and each separate word will be capitalized to provide the title of your page.
http://www.nunit.org/wiki/doku.php?id=extras:my_cool_extension&do=edit&rev=0
2. Fill in the items in the header, leaving a single space after the colon in each line.
- Extension Type: Addin, Addon, Runner or Extra
- Author: the name of the author or authors of the extension
- Description: a one line description for use on the summary page
- License: the name of the license you use, if it has one, or Other
- NUnitVersion: the range of NUnit versions your extension works with
- PlatformSupport: list platforms the extension is known to work on, e.g: All, Windows, Linux, etc.
3. Complete the body of the page with information about your extension. If clarification is needed regarding NUnit versions and platforms you support, include a section here.
4. Save your edit. Your extension will be listed automatically on the summary page so that others can find it.
