nsubstitute

I have an interface with a number of generic methods. These methods perform operations based on the type of data that is passed in. How do I mock this with NSubstitute? At the moment, I had to resort to using a concrete class instead of a mock since I cannot handle all possible types that the method will be called with. public interface IInstanceSource { bool CanCreate<T>(); T Create<T>(); void Register<T>(Func<T> creator); } public static IInstanceSource GetInstanceSource() { var _data = new Dictionary<Type, Func<object>>(); var a = Substitute.For<IInstanceSource>(); //code below fails since

I am using the [AutoNSubstituteData] attribute, which was posted here: AutoFixture, xUnit.net, and Auto Mocking I would like to combine this with the [PropertyData("")] attribute from xunit extensions. This is my test: public static IEnumerable<string[]> InvalidInvariant { get { yield return new string[] { null }; yield return new [] { string.Empty }; yield return new [] { " " }; } } [Theory, AutoNSubstituteData, PropertyData("InvalidInvariant")] public void TestThatGuardsAreTriggeredWhenConnectionStringArgumentIsInvalid( IDeal deal, IDbConnection conn, IDb db, ISender sender, string

I want to verify that a method on my NSubstitute mock is called with a particular array argument. Say the interface, IProcessor , has a method void ProcessSomething(Foo[] something]) . Say my class under test is named Commander . I set up my test like this: //prepare var processor = Substitute.For<IProcessor>; var commander = new Commander(processor); var foo1 = new Foo("alpha"); var foo2 = new Foo("bravo"); var foos = new [] {foo1, foo2}; //act commander.DoSomething(foo1, foo2); //verify processor.Received().ProcessSomething(foos); // FAILS The Received() call fails with: NSubstitute

I have a unit test where I use .Returns() to return some sample data: [TestMethod] public void TestRetrieveElementsInVersion() { IRetrieveElementSequence component = Substitute.For<IRetrieveElementSequence>(); List<UnconstructedElement> list = new List<UnconstructedElement> { new UnconstructedElement{Version = "1"}, new UnconstructedElement{Version = "2"} }; component.RetrieveElements().Returns(list); // exception reported here const string target = "1"; IRetrieveElementSequence service = new RetrieveElementsInAVersion(component, target); IList<UnconstructedElement> result = service

I am using the repository pattern in an MVC 3 application I am currently developing. My repository interface looks as follows: public interface IRepository<TEntity> where TEntity : IdEntity { void Add(TEntity entity); void Update(TEntity entity); void Remove(TEntity entity); TEntity GetById(int id); IList<TEntity> GetAll(); TEntity FindFirst(Expression<Func<TEntity, bool>> criteria); IList<TEntity> Find(Expression<Func<TEntity, bool>> criteria); } In a lot of instances, when coding methods in my service classes, I am using the FindFirst and Find methods. As you can see, they both take a linq