In my last post I gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using Visual Studio 2012 and Moq. The sample code in that post was extremely simple, so I wanted to follow up with a more complex example that shows how to test »
In my last post I explained why you should unit test your Dynamics CRM-facing code using frameworks to handle both testing automation and mock objects. In this post, I'm going to provide an overview of how to get started. As I mentioned last time, we'll be using the unit testing »
When writing custom code that interacts with Microsoft Dynamics CRM, it is important to: Unit test your code Use an automated unit testing framework to automate your unit tests Write unit tests that do not depend on external resources such as a Microsoft Dynamics CRM application server or SQL Server »
Back in January, after I published my How to unit test C# Dynamics CRM interface code - part III post on how to use NUnit and Moq to test Dynamics CRM interfacing code, I uploaded my project files to the MSDN code gallery. Earlier this week I revisited my original »
In parts one and two of this series, I gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using NUnit and Moq, and I showed code samples for a couple of different scenarios. In this post I will show how to work with CRM metadata »