I figured out my issue. It was the change from the default Repeat.Once () to Repeat.Any() that hosed us. We were relying on Repeat.Once() in several areas.
On Jul 15, 10:42 am, Adam Tybor <[email protected]> wrote: > I just upgraded my rhino.mocks assemblies from trunk in my project. I > was previously on 3.5, now I am on trunk with trunk of Castle > DynamicProxy and a bunch of tests are now failing with the following > simple scenario. > > [Test, Description("Passes as it should")] > public void ShouldRespectAPropertySetOnAStub() > { > var foo = MockRepository.GenerateStub<IFoo>(); > foo.Str = "Adam"; > > Assert.AreEqual("Adam", foo.Str); > > } > > [Test, Ignore("Why is this failing?")] > public void ShouldRespectAPropertySetOnAMock() > { > var foo = MockRepository.GenerateMock<IFoo>(); > foo.Str = "Adam"; > > Assert.AreEqual("Adam", foo.Str); > > } > > Is this a breaking change in Rhino.Mocks or is this a DP issue under > the covers. > > Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/RhinoMocks?hl=en -~----------~----~----~----~------~----~------~--~---
