Skip to content
Roslyn analyzers for writing unit tests with NUnit
Branch: master
Clone or download
mikkelbu Merge pull request #127 from mikkelbu/replace-licenseUrl
Replace licenseUrl-element with license-element
Latest commit eab0967 Apr 23, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Merge pull request #127 from mikkelbu/replace-licenseUrl Apr 23, 2019
.editorconfig Fix comments on PR. Mar 26, 2018
.gitignore Create Mar 10, 2018 Update README and move content to CONTRIBUTING Apr 17, 2019 Update README and move content to CONTRIBUTING Apr 17, 2019
appveyor.yml Make Appveyor run tests before creating nuget package Jun 17, 2018
build.cake Upload test results to AppVeyor Dec 17, 2018
build.ps1 Add initial cake script Mar 19, 2018
license.txt Initial commit Nov 26, 2016

NUnit Analyzers

Build status MyGet Feed

This is a suite of analyzers that target the NUnit testing framework. Right now, the code is separate from the NUnit framework, so if you want to try out the analyzers you'll need to download the analyzers separately as a nuget package. In the future the analyzers may be added as part of the NUnit framework package but that hasn't been done yet.


Prerelease nuget packages can be found on MyGet. Please try out the package and report bugs and feature requests.


Below we give two examples of analyzers. One will look for methods with the [TestCase] attribute and makes sure the argument values are correct for the types of the method parameters along with the ExpectedResult value if it is provided.

testcase analyzers

The other analyzer looks for classic model assertions (e.g. Assert.AreEqual(), Assert.IsTrue(), etc.). This analyzer contains a fixer that can translate the classic model assertions into constraint model assertions (Assert.That()). classic model assertions analyzers


NUnit analyzers are Open Source software and released under the MIT license, which allow the use of the analyzers in free and commercial applications and libraries without restrictions.


There are several ways to contribute to this project. One can try things out, report bugs, propose improvements and new functionality, work on issues (especially the issues marked with the labels help wanted and Good First Issue), and in general join in the conversations. See Contributing for more information.

This project has adopted the Code of Conduct from the Contributor Covenant, version 1.4, available at See the Code of Conduct for more information.


NUnit.Analyzers was created by Jason Bock. A complete list of contributors can be found on the GitHub contributors page.

You can’t perform that action at this time.