** Project changed: nunit-3.0 => nunitv2
** Changed in: nunitv2
Importance: Undecided => Medium
** Changed in: nunitv2
Assignee: (unassigned) => Charlie Poole (charlie.poole)
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant
You have been subscribed to a public bug:
I have a VS2010 solution with projects built using the .NET 4 framework.
I have the debug options set to run nunit.exe and load my unit test
project.
However, even when setting the runtime in NUnit 2.5.7 to use that
framework, breakpoints are not hit in V
I haven't seen your note on the NUnit list yet, so I'll answer here.
In the past, NUnit was using transforms to create console output, not
reports - although you could redirect the console output to a file and
call it a report if you liked. XSL transforms are a logical way to go
for reports, but a
You have been subscribed to a public bug:
The NUnit Configuration Section is used for the following settings in nunit v2:
* OldStyleTestCases
* ApartmentState
* ThreadPriority
* DefaultLogThreshold
These settings are viewed as depending upon an individual project, which is why
they are n
Ok,
I think that worse case, we could see if we can embed the resource
ourselves if you have no need for it. That said, I would be interested
in what you did to replace your reliance on the resource. If we can
incorporate a similar method, I would rather go that route.
Thanks,
Ryan
--
You rec
** Changed in: nunit-3.0
Status: Confirmed => Triaged
** Changed in: nunit-3.0
Importance: Undecided => Medium
** Changed in: nunit-3.0
Milestone: None => 2.9.6
** Changed in: nunit-3.0
Assignee: (unassigned) => Charlie Poole (charlie.poole)
--
You received this bug notifica
** Branch linked: lp:nunit-3.0
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/920472
Title:
CollectionAssert.IsNotEmpty must dispose Enumerator
Status in NUnit Test Framework
** Changed in: nunit-3.0
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/920472
Title:
CollectionAssert.IsNotEmpty must dispose Enumerat
** Branch linked: lp:nunitv2
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/920472
Title:
CollectionAssert.IsNotEmpty must dispose Enumerator
Status in NUnit Test Framework:
** Changed in: nunitv2
Assignee: (unassigned) => Charlie Poole (charlie.poole)
** Changed in: nunit-3.0
Assignee: (unassigned) => Charlie Poole (charlie.poole)
** Changed in: nunit-3.0
Milestone: None => 2.9.6
** Changed in: nunitv2
Status: Triaged => Fix Committed
--
You
Ah! I had not noticed that you were the originator of the bug.
I haven't seen your post arrive yet, but I'll reply when I do. In a
pinch, we could
just leave the unused resource in NUnit 2.6 and uncomment those lines.
Otherwise, I'll keep this bug to remind me to remove all traces of the unused
r
Actually, I figured out that NAnt still relied on it. The error came from a
method in the nunit2 task. See line 360 here:
https://github.com/nant/nant/blob/master/src/NAnt.NUnit/NUnit2/NUnit2Task.cs
If this is this case, go ahead and close out this bug. I posted
something related to this in th
NUnit no longer uses an xslt transform to produce its console output as it
once did. So the error is a bit of a mystery.
What command line are you using with nunit-console in order to get this
error?
Does it give you a stack trace?
Is it possible that you are mixing versions of NUnit?
--
You r
** Also affects: nunit-3.0
Importance: Undecided
Status: New
** Changed in: nunit-3.0
Status: New => Triaged
** Changed in: nunit-3.0
Importance: Undecided => Low
--
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant
** Changed in: nunitv2
Status: New => Triaged
** Changed in: nunitv2
Importance: Undecided => Low
--
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/920472
Title:
CollectionAssert.IsNot
Public bug reported:
protected static bool IsEmpty(IEnumerable enumerable)
{
ICollection collection = enumerable as ICollection;
if (collection != null)
return collection.Count == 0;
else
return !enumerable.GetEnumerator().MoveNext();
}
enumerable.Get
Public bug reported:
Using v2.6.0.12017, we're receiving socket exceptions after the unit
tests have completed their execution. This is causing our continuous
integration tests to fail even though the unit tests have successfully
executed.
Tests run: 12, Errors: 0, Failures: 0, Inconclusive: 0,
17 matches
Mail list logo
