nunit / nunit-silverlight

The Silverlight version of the NUnit 3 Framework

NUnit 4 Framework

NUnit is a unit-testing framework for all .NET languages. It can run on macOS, Linux and Windows operating systems. NUnit can be used for a wide range of testing, from unit testing with TDD to full fledged system and integration testing. It is a non-opinionated, broad and deep framework with multiple different ways to assert that your code behaves as expected. Many aspects of NUnit can be extended to suit your specific purposes.

The latest version, version 4, is an upgrade from the groundbreaking NUnit 3 framework. It is a modernized version, aimed at taking advantage of the latest .NET features and C# language constructs.

If you are upgrading from NUnit 3, be aware of the breaking changes. Please see the NUnit 4 Migration Guide and take care to prepare your NUnit 3 code before you do the upgrade.

Table of Contents

• Downloads
• Documentation
• Contributing
• License
• NUnit Projects

Downloads

The latest stable release of the NUnit Framework is available on NuGet or can be downloaded from GitHub. Pre-release builds are available on MyGet.

Documentation

Documentation for all NUnit projects can be found at the documentation site.

• NUnit Documentation
• Installation
• Release Notes
• Code Samples

Contributing

For more information on contributing to the NUnit project, please see CONTRIBUTING.md and the Developer Docs.

NUnit 3.0 was created by Charlie Poole, Rob Prouse, Simone Busoli, Neil Colvin and numerous community contributors. A complete list of contributors since NUnit migrated to GitHub can be found on GitHub.

Earlier versions of NUnit were developed by Charlie Poole, James W. Newkirk, Alexei A. Vorontsov, Michael C. Two and Philip A. Craig.

License

NUnit is Open Source software and NUnit 4 is released under the MIT license. Earlier releases used the NUnit license. Both of these licenses allow the use of NUnit in free and commercial applications and libraries without restrictions.

NUnit Projects

NUnit is made up of several projects. When reporting issues, please try to report issues in the correct project.

Core Projects

• NUnit Test Framework - The test framework used to write NUnit tests (this repository)
• NUnit Visual Studio Adapter - Visual Studio/Dotnet adapter for running NUnit 3 and 4 tests in Visual Studio or the dotnet command line.
• NUnit Console and Engine - Runs unit tests from the command line and provides the engine that is used by other test runners to run NUnit tests.

Visual Studio Extensions

• NUnit Visual Studio Adapter - Visual Studio adapter for running NUnit 3 and 4 tests in Visual Studio or the dotnet command line.
• NUnit Visual Studio Templates - Project templates and snippets for writing unit tests in Visual Studio. This repo is for reference only, as the templates have been donated to the Dotnet project and are maintained there, and also released as part of the dotnet releases.
• Visual Studio Test Generator - Generates NUnit tests in Visual Studio
• NUnit 2 Visual Studio Adapter - Visual Studio adapter for running older NUnit 2.x tests in Visual Studio and in VSTS/TFS builds

NUnit Engine Extensions

• NUnit 2 Driver - Allows the NUnit 3 engine to run NUnit 2 tests
• NUnit 2 Result Writer - Writes test results in the legacy NUnit 2 format
• Visual Studio Project Loader - Loads and parses Visual Studio projects and solutions
• NUnit Project Loader - Loads NUnit projects

nunit-silverlight's Issues

NunitLite (SL50) cannot be used in CI (params not working)

@Stift commented on Tue Apr 26 2016

Currently the NunitLite Runner for Silverlight does not work as expected. Parameters like --output or --teamcity do not work, because when they are actually used in the code by the runner, they are ignored because the specific code parts are excluded with directives.
Unfortunately the --help page shows these options as enabled.

The problem is that I don't get any result that can be parsed by any CI server. Neither XML or console ouput.

---

@CharliePoole commented on Tue Apr 26 2016

That runner is very simple and was primarily created so we could run our own CI tests. As you probably noticed, it's not even mentionned in the docs.

The runner is a .NET 4.5 console application, but links to the Silverlight builds of nunitlite and nunit.framework. Silverlight, of course, doesn't support the console but does direct it's output back to the runner, which prints it.

Bottom line, to make these options work, we would have to implement them in the runner, probably copying the code from nunitlite to do so. It's doable but we need to figure out if we want to support the silverlight runner for general use.

---

@Stift commented on Wed Apr 27 2016

I'm relatively sure, that I read in the docs that for silverlight you definetly have to take the nunitlite stuff (https://github.com/nunit/docs/wiki/Installation). I understand that you struggle with silverlight support, I think that is common sense nowadays. But currently you distribute nunit.sl50 and nunitlite.sl50 with nearly the latest version. How are they intended to use then, when there is no runner? For a silverlight project I can't create an exe, and the console-runner also does not work.

---

@CharliePoole commented on Wed Apr 27 2016

The question of how to run Silorverlight tests has always been a rather open one, even in the original NUnitLite implementation. That's because we have never had any contributors who actually work in Silverlight. At one time I had a primitive implementation that worked with the Microsoft runner but we settled on the technique we use ourselves to test nunit - Silverlight tests are expected to be Silverlight applications that use NUnitLite. If you look at the nunit framework tests for silverlight, you will see that approach.

However, that only works on the desktop, not as a CI runner. So, a few months ago, I added the silverlight "runner", a console app that references silverlight and runs the tests m.ostly using Silverlight - but with a console available for display.

Neither approach to running Silverlight tests is documented, I'm afraid, so your confusion is understandable. To put it another way... we've been waiting to hear from some Silverlight devs. :-)

---

@CharliePoole commented on Wed Apr 27 2016

I'd definitely like to see us document what we do have and maybe add output redirection to the runner. In the longer run, I'd like to be able to run Silverlight tests from the console runern. Even though little new work is done with Silverlight these days, the exercise of making it work with the console runner would teach us something about the best way to interact with other platforms.

---

@rprouse commented on Tue Oct 25 2016

Thanks for the idea, but we are spinning SL out into it's own repository and putting it into maintenance mode unless someone from the SL community wants to pick it up and move it forward.