Geek Answers Handbook

Rhino Mocks vs Moq for Silverlight

We are the Silverlight Unit Test Framework for testing.

Which one will be better for my team? Rhino Mocks or Moq. No one has experience using such a structure.

What are the advantages and disadvantages of using each environment in this environment?

+4
source share
4 answers

Take a look at both and see what kind of syntax sets you use and the skills of your team.

Rhino Mocks has been around for 4 years and supports a couple of different symmatics. Recording / playback is the oldest, and Ass Arrange Act Assert (AAA) is the newest. I would say that in the Rhino community, Mocks is a standard structure because of how long it has been around and how easy it is to find examples, documentation, and help.

Moq is valid for about 1 year, and relies heavily on .Net 3.5 syntax like lambdas. I think that because of how new this is, it can be harder to find people who have used it and get help.

More important than the structure you choose is an understanding of how layouts help you test, as well as how they can change the way you think about developing systems to test. After all, structure does not matter; experience and knowledge matter.

+7
source

There is not much influence Silverlight has on frameworks, and using them is not much different from what makes it completely .NET.

RM is believed to have a steeper learning curve, and MoQ is said to have a cleaner API, but RM, on the other hand, works much longer and probably supports more short-case scenarios.

I would recommend a splash with both, and choosing what suits you is best for you.

+1
source

I prefer Moq for its syntax, similar to lamba.

0
source

It’s very difficult for me to use Moq with ref / out parameters in function settings ... Because of this, I switched to Rhino

0
source

More articles:


All Articles