MOQ is a framework for mocking method calls and returns in unit tests. While MOQ allows testing functionality by mocking returns, it cannot test actual database retrieval or other real functionality. Therefore, MOQ is not the end of unit testing, and developers still need to write unit tests that exercise real functionality like database transactions. The document is a white paper by Ramasubramanian Thumati Rajendran discussing whether MOQ constitutes the end of unit testing.

1. IS MOQ END OF UNIT TESTING?
White Paper
June2016
INTRODUCTION
The conceptof mocking the unit tests is aroundfor some time now.My question is, “Is MOQthe end of
unit testing”.
MOCK TESTS
The behavior of the applications can be mocked and tested. For example, using MOQ framework, the
return value of a method call can be mocked to return custom values. The custom values then can be
matchedwith the expectedvalue to findoutif the methodhas performedcorrectly.MOQcanbe usedto
test if a particular method has been called and/or how many times it has been called to test the
functionality.
WHY THE QUESTION?
Using MOQ, we cannottest some of the actual functionality, for example testing the retrieval from the
database.
AND THE ANSWER IS
MOQ is NOT the end of unit testing. Still the developer needs to unit test the real functionalities (for
example database transactions).
ABOUT THE AUTHOR
Ramasubramanian Thumati Rajendran has over 15 years of experience in technologies ranging from
FoxPro,VisualBasic,.NET,SharePoint,SQLServer, Oracle,and MSBI.Heis workingasa senior architect
with SwordGlobal India P Ltd, Chennai, India managing MicrosoftAzure,SharePoint and .Net projects.
Hecanbe reachedat Ramasubramanian.r@sword-in.com.Alternately,hecanbereachedat hispersonal
email ram.thumati@gmail.com.