Bug 13280 - Non-NUnit pieces need to be factored out of Nunit addin
Summary: Non-NUnit pieces need to be factored out of Nunit addin
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: NUnit ()
Version: Trunk
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: master
Assignee: Lluis Sanchez
Depends on:
Reported: 2013-07-16 19:13 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-09-26 12:52 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Mikayla Hutchinson [MSFT] 2013-07-16 19:13:45 UTC
Currently it's not obvious how to plug in new test runners. The Unit testing addin mixes together the runner-agnostic extension points and infrastructure with the NUnit specific implementations. Worse, many of the core pieces have "NUnit" in the name and the NUnit specific pieces do not.

IMO it needs to be split into two addins, MonoDevelop.UnitTesting and MonoDevelop.UnitTesting.NUnit.
Comment 1 Marius Ungureanu 2017-09-26 12:52:25 UTC
Lluis took care of this some time ago when adding NUnit2/3 support.