Charlie Poole
2008-08-29 17:26:39 UTC
What would folks like to see as an alternative name?
_____
From: nunit-users-***@lists.sourceforge.net
[mailto:nunit-users-***@lists.sourceforge.net] On Behalf Of Craig A.
Ritchie
Sent: Friday, August 29, 2008 4:41 AM
To: nunit-***@lists.sourceforge.net
Subject: [Nunit-users] Name Collision
Not sure if this has been discussed or reported as of yet but NUnit 2.5
Alpha 3 has a class called AssertionHelper class that has a method called
Expect(). When inheriting from AssertionHelper in my test class and then
using Rhino.Mocks within my test I get some naming collision with this
Expect method as Rhino.Mocks has a static class named Expect. I know there
are simple ways around this but since more than likely these two testing
tools are used together quite a bit NUnit 2.5 might want to address this in
a future release if AssertionHelper is going to hang around.
-Craig
_____
From: nunit-users-***@lists.sourceforge.net
[mailto:nunit-users-***@lists.sourceforge.net] On Behalf Of Craig A.
Ritchie
Sent: Friday, August 29, 2008 4:41 AM
To: nunit-***@lists.sourceforge.net
Subject: [Nunit-users] Name Collision
Not sure if this has been discussed or reported as of yet but NUnit 2.5
Alpha 3 has a class called AssertionHelper class that has a method called
Expect(). When inheriting from AssertionHelper in my test class and then
using Rhino.Mocks within my test I get some naming collision with this
Expect method as Rhino.Mocks has a static class named Expect. I know there
are simple ways around this but since more than likely these two testing
tools are used together quite a bit NUnit 2.5 might want to address this in
a future release if AssertionHelper is going to hang around.
-Craig