Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1360389 - Upgrade to NUnit 3.x
Summary: Upgrade to NUnit 3.x
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nunit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Timotheus Pokorra
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1360620
Blocks: 1313236
TreeView+ depends on / blocked
 
Reported: 2016-07-26 14:54 UTC by Timotheus Pokorra
Modified: 2016-08-09 10:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-09 10:34:41 UTC


Attachments (Terms of Use)

Description Timotheus Pokorra 2016-07-26 14:54:19 UTC
Current version in Fedora Rawhide is NUnit 2.6.4

There is currently NUnit 3.4.1 available at https://github.com/nunit/nunit/releases/tag/3.4.1

This is also required for MonoDevelop 6.0

Problem is that the NUnit gui has been split from NUnit 3.x, and the current state is not stable yet. see https://github.com/nunit/nunit-gui

So we cannot just replace NUnit 2.x with NUnit 3.x plus a new nunit-gui package yet.

The suggestion from Claudio was to add a package nunit2 for compatibility. https://bugzilla.redhat.com/show_bug.cgi?id=1313236#c4

Comment 1 Timotheus Pokorra 2016-07-26 19:42:05 UTC
I have done some preparation work:
https://github.com/tpokorra/lbs-mono-fedora/tree/master/nunit upgraded to NUnit 3.4.1
and
https://github.com/tpokorra/lbs-mono-fedora/tree/master/nunit2 provides the legacy NUnit2 and nunit2-gui package

I will put that into rawhide when it proves to work in the copr (https://copr.fedorainfracloud.org/coprs/tpokorra/mono/) first


Note You need to log in before you can comment on or make changes to this bug.