I'm not entirely sure what this test achieves to be honest, other than
testing parallel execution of methods on a single proxy instance (as
haifisch mentions) as provided by Rhino
You have an interface which I imagine represents some dependency for your
SUT (software under test)
Then you create your mock (which should be used to mock a dependency passed
in to your SUT)
But then you attempt to get it involved in some threading stuff. Why would
you want to do that?
Surely such a test belongs with the implementation of this interface (i.e.
the class), I can foresee no reason to include such a thing in your tests.
--
You received this message because you are subscribed to the Google Groups
"Rhino.Mocks" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/rhinomocks.
For more options, visit https://groups.google.com/d/optout.
