https://alexanderdevelopment.net/tag/unit-testing/Recent content in unit-testing on Alexander DevelopmentHugo -- gohugo.ioen-usThu, 24 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-7-web-requests/Thu, 24 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-7-web-requests/One of the main points of all my unit testing posts is that unit tests should be written so that you can test your code without needing to rely on external resources, and, we’ve been able to use Moq as a stand-in for Dynamics CRM’s related services without too much trouble.https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-8-exception-raising/Thu, 24 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/24/unit-testing-custom-microsoft-dynamics-crm-code-part-8-exception-raising/This is the final post in my series on unit testing custom Microsoft Dynamics CRM code in which I’ve been showing how you can unit test custom C# code that interacts with Microsoft Dynamics CRM using Visual Studio’s unit testing tools and Moq. We’ve looked at several different scenarios thus far, but none of them included the method under test throwing an exception.https://alexanderdevelopment.net/post/2013/10/21/unit-testing-custom-microsoft-dynamics-crm-code-part-6-plug-ins/Mon, 21 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/21/unit-testing-custom-microsoft-dynamics-crm-code-part-6-plug-ins/In my last post, I showed how to unit test a Microsoft Dynamics CRM custom workflow activity using Visual Studio and Moq. In this post I will show you how to unit test a Dynamics CRM plug-in. For this example we’ll be using the sample FollowupPlugin class in the CRM 2011 SDK, but the principles I will demonstrate are applicable to any plug-in.https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-5/Thu, 17 Oct 2013 18:00:00 +0000https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-5/In the last three posts of this series, I showed how to unit test Microsoft Dynamics CRM C# interfaces code with mock objects using Visual Studio 2012 and Moq. In this post, I will show how to unit test custom workflow activities that are executed by Dynamics CRM processes. I will be using the regular expression validation custom workflow activity I showed in my “Using regular expressions in Dynamics CRM 2011 processes” post.https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-4/Thu, 17 Oct 2013 17:00:00 +0000https://alexanderdevelopment.net/post/2013/10/17/unit-testing-custom-microsoft-dynamics-crm-code-part-4/In parts two and three of this series, I gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using Visual Studio 2012 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 (optionset values, statuscode values, etc.https://alexanderdevelopment.net/post/2013/10/10/unit-testing-custom-microsoft-dynamics-crm-code-part-3/Thu, 10 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/10/unit-testing-custom-microsoft-dynamics-crm-code-part-3/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 multiple calls to the CRM web service instead of just a single one.https://alexanderdevelopment.net/post/2013/10/09/unit-testing-custom-microsoft-dynamics-crm-code-part-2/Wed, 09 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/09/unit-testing-custom-microsoft-dynamics-crm-code-part-2/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 tools included in Visual Studio 2012 for the unit testing automation and Moq for the object mocking.https://alexanderdevelopment.net/post/2013/10/02/unit-testing-custom-microsoft-dynamics-crm-code-part-1/Wed, 02 Oct 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/10/02/unit-testing-custom-microsoft-dynamics-crm-code-part-1/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 Over the course of my next several posts, I’ll be showing you some best practices for unit testing Dynamics CRM-facing code using Visual Studio unit testing tools and the Moq object mocking library.https://alexanderdevelopment.net/post/2013/05/01/updated-unit-testing-dynamics-crm-c-interfaces-code-using-nunit-and-moq-code-sample/Wed, 01 May 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/05/01/updated-unit-testing-dynamics-crm-c-interfaces-code-using-nunit-and-moq-code-sample/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 solution while preparing a demo for some of my colleagues.https://alexanderdevelopment.net/post/2013/01/13/how-to-unit-test-c-dynamics-crm-interface-code-part-iii/Sun, 13 Jan 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/01/13/how-to-unit-test-c-dynamics-crm-interface-code-part-iii/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 (optionset values, statuscode values, etc.https://alexanderdevelopment.net/post/2013/01/09/how-to-unit-test-c-dynamics-crm-interface-code-part-ii/Wed, 09 Jan 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/01/09/how-to-unit-test-c-dynamics-crm-interface-code-part-ii/Earlier this week I wrote a post that gave an introduction to unit testing Dynamics CRM C# interfaces code with mock objects using NUnit 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 multiple calls to the CRM web service instead of just a single one.https://alexanderdevelopment.net/post/2013/01/06/how-to-unit-test-c-sharp-dynamics-crm-interfaces-code/Sun, 06 Jan 2013 00:00:00 +0000https://alexanderdevelopment.net/post/2013/01/06/how-to-unit-test-c-sharp-dynamics-crm-interfaces-code/A while back I wrote a post that gave a high-level overview of some of the tools I had used at a previous job to do unit testing of Dynamics CRM interfaces code, but I didn’t get into the why or how. Here is an introduction to unit testing Dynamics CRM code using an automated unit testing framework and a mock object framework.https://alexanderdevelopment.net/post/2011/04/01/unit-testing-microsoft-dynamics-crm-code/Fri, 01 Apr 2011 00:00:00 +0000https://alexanderdevelopment.net/post/2011/04/01/unit-testing-microsoft-dynamics-crm-code/If you’re developing code that runs against Dynamics CRM, you know you should be testing it, right? As a developer first and foremost, I always believed that tests and documentation got in the way of the important - and more fun - stuff, but as I transitioned into a management role with responsibility for my company’s Dynamics CRM system, I began to appreciate the value of the less-fun stuff.