DotNetKicks.com - Stories tagged with TDD

Dev Magic Fake Framework Released on CodePlex

Tue, 06 Sep 2011 15:18:53 GMT

Dev Magic Fake is a faking framework and open source project that provides the ability to focus on how to complete, verify and test the application behaviors and response without focus on coding or developing the underline layers until the application features finished, tested and approved

Docx 2 UnitTest

Thu, 13 May 2010 01:16:53 GMT

A Visual Studio 2010 custom tool to generate unit tests from Microsoft® Word® 2007/2010 documents.

Docx 2 UnitTest

Thu, 13 May 2010 01:16:53 GMT

A Visual Studio 2010 custom tool to generate unit tests from Microsoft® Word® 2007/2010 documents.

Unit Testable WCF Web Services in MVVM and Silverlight 4

Thu, 15 Apr 2010 13:15:07 GMT

I figured that there has to be a better way to solve this everyday problem so while working on my personal MVVM framework (yes, everyone is building one these days) i was setting these goals regarding the Web Service calls from my MVVM applications: 1. simplify as much as possible asynchronous invocation of Web Service methods (avoid writing boring boilerplate code for each call) 2. get rid of the Add Service Reference approach completely if possible 3. make the Web Services unit testable (hide them behind some interface so we can mock them in our unit tests) 4. simplify exception handling 5. fault tolerance (if web service client is faulted by exception it should be automatically recreated) ...

Auto-mocking hierarchies (a.k.a. recursive mocks) with Moq

Thu, 27 Aug 2009 16:53:20 GMT

In this post I will show how the auto-mocking hierarchies (a.k.a. recursive mocks) feature of Moq can greatly simplify your unit tests.

ASP.NET MVC, TDD and Fluent Validation

Fri, 21 Aug 2009 02:00:02 GMT

"Yesterday I wrote about ASP.NET MVC, TDD and AutoMapper, and how you can use them together in a DDD application. Today I thought I would follow up and explain how to apply these techniques to another important (but boring) part of any web application: user input validation."

Introduction to Test-Driven Development with ASP.NET MVC

Thu, 23 Jul 2009 03:09:40 GMT

Introduction to Test-Driven Development (TDD) with ASP.NET MVC.

ASP.NET MVC TDD using Visual Studio 2010

Wed, 10 Jun 2009 10:15:07 GMT

Phil Haack announced yesterday that the tooling support for ASP.NET MVC is available for Visual Studio 2010. Troy Goode already blogged about the designer snippets (which are really really cool, just like other parts of the roadmap for ASP.NET MVC 2.0). I'll give the new TDD workflow introduced in VS2010 a take.

A Software Craftsman's 200$ Bookshelf Upgrade!

Thu, 28 May 2009 08:54:16 GMT

About three weeks ago, I asked my readers and some people in the Norwegian developer community about what books they have in their bookshelf. The response was good, and I ended up with many good book recommendations. Today I placed a new order on Amazon, and spent 200$ to upgrade my bookshelf. If you read further, you'll see which books I ordered.

Toward a Better Use of Context/Specification

Wed, 27 May 2009 23:41:19 GMT

have you hand-rolled your own base class for your Context/Specification style specs? Curious whats different between a Context/Specification base class and a typical unit testing base class? read on...

Redefining ALT.NET or rather, rediscovering it's meaning

Mon, 25 May 2009 02:09:08 GMT

I've heard about ALT.NET about a year ago. At first, I thought that it was about using alternatives to Microsoft or to avoid Microsoft software. ALT.NET was supposed to be about going "alternative" and being against "The Man" and being for "The People". Well, I must agree that I wasn't totally right with that. I mean, Microsoft make some mess but it also does a lot of great tools and particularly a great IDE with lots of extensibility point. Then, I did what I should have done in the beginning. I looked up the definition.

Unit testing WCF services through dependency injection

Mon, 18 May 2009 15:24:58 GMT

"When building a WCF service in an enterprise application, this service frequently depends on other services or resources. When creating unit tests for this service, we don't want to host all these other services over WCF endpoints. Instead we will most likely want to inject mock objects. In some case we may even want to inject some in-process instances of these other services."

The Wonders Of InternalsVisibleTo

Fri, 08 May 2009 02:19:43 GMT

Demonstrates how to expose an assembly's internal parts to "friend" classes using the InternalsVisibleTo attribute.

The best way to learn new API's; TDD!

Mon, 04 May 2009 18:31:04 GMT

In this post I will tell you a story about how I used TDD (Test Driven Development) to learn new a new API, and how I successfully managed to accomplish my task before expected, and delivered 100% working code (no defects), even though I did something I've never done before - interested? I thought so ;)

Kona: Continuous Integration and Better Unit Testing

Mon, 13 Apr 2009 11:01:02 GMT

In this screencast Rob Conery and Brad Wilson talk about continuous integration with TeamCity, Unit Testing with xUnit and TDD in general. "This screencast went from a simple idea - talking to Brad Wilson about better Unit Testing - to some pretty broad topics such as source control, unit testing, and continuous integration. I seriously could have written a whole book based on the stuff flying through my mind. I reigned it in a bit and decided to focus on two things that I don't think get enough press: writing a good Unit Test coupled with Continuous Integration."

DDD & TDD using EF, Part 2.A Unit Testing Entities With Moq3

Wed, 25 Mar 2009 01:26:11 GMT

I had few previous posts about DDD & TDD with Entity Framework that you might need to return to them before you proceed with this post. To summarize these posts, I was trying to build testable Models that is based on EF. But EF doesn't support Persistence Ignorance in its first version which make testing it in most cases require a database connection where you can test you code against it. My target was to build a testable models based on EF and that is independent of any underlying data source.

Eliminating ToList().ForEach() by TDD and Extensions Methods

Sun, 08 Mar 2009 15:17:45 GMT

Following "Program to an interface, not an implementation", you should use IList instead of List. However, you then lose access to some great delegate methods of the List class (e.g. ForEach, ConvertAll). In order to use them you have to first call ToList(). In this post I will use Test Driven Development (TDD) to add these as extension methods to the generic IEnumerable interface, elimintating the need to call ToList().

Unit Testable Configuration Manager - Kazi Manzur Rashid's Blog

Tue, 03 Mar 2009 19:31:19 GMT

If you are a TDD purist, you should know that accessing file system in Unit Test is violating the rule. But in our application, our infrastructural code often requires to access the configuration values form web.config/app.config. In this post, I will show you how can create a simple wrapper class which you can use in your unit tests without hitting the file ...

TDD: How I applied TDD to a simple problem

Sun, 01 Mar 2009 07:45:30 GMT

A month or two ago I had to built a component that had to analyse a string a return some information out of it. The best result for this was a Regular Expression and I was sure. So I started writing what kind of input would be valid and which one should not be allowed.

Implementing UnitOfWork Pattern In Linq To SQL Application

Fri, 27 Feb 2009 12:46:02 GMT

Implementing UnitOfWork Pattern In Linq To SQL Application In my previous post, I have shown how to create Linq to Sql Repository which will have the maximum code coverage, In this post, I will show a simple UnitOfWork class which will flash the changes back to your database. I will be again use my ongoing UnityCommonServiceLocatorMVC project. Lets assume that in your ASP.NET MVC application you have a method in your controller which will add a category and its associate product in the Northwind database.

Implementing UnitOfWork Pattern In Linq To SQL Application

Fri, 27 Feb 2009 12:46:02 GMT

Implementing UnitOfWork Pattern In Linq To SQL Application

Fri, 27 Feb 2009 12:46:02 GMT

Domain Driven Design & Test Driven Design\Development with Entity Fram

Wed, 25 Feb 2009 00:42:42 GMT

decided to provide some integration testing before proceeding as a proof of concept. In integration testing I will connect to the database and perform unit testing while connecting to the database.\ This unit test is almost identical to the one in my previous post. Except here I am testing the results that is coming out from EF and Database. My target is to test IDataContext Implemented methods in NorthwindDataContext

Domain Model (Developing KiGG v2.0 Part 1) - Kazi Manzur Rashid's Blog

Thu, 12 Feb 2009 22:31:05 GMT

As mention in my previous post that I will be discussing the technical side of **KiGG**. So this is the beginning and it will be a multi-part series. I will try to put as much detail as possible, do let me know if I missed anything. Just for a recap, KiGG is Web 2.0 style social news application where I am trying to exercise some of the best practice like TDD, DDD, SOLID etc with Microsoft supported tooling. If you want to see it in action just visit http://dotnetshoutout.com . KiGG is already a fully functional application, but here I am starting from scratch, so the actual code might not look the same with following but it will show you how it is evolved as I am going to post more on it over the time.

DDD & TDD with Entity Framework, Part 1.a Refactoring & Unit Testing

Wed, 11 Feb 2009 06:03:11 GMT

In previous post I talked about building domain model for Northwind using Entity Framework. I used the generated ObjectContext class which is NorthwindDataContext as the basic Data Access Layer Helper. But my NorthwindDataContext is implementing custom interface I created in order to be able to make my Data Access Layer testable as well as to be independent from EF. My target is to achieve decoupling between EF and all layers above it. This include Repository classes. This might not be of a big benefit to everyone, because my repositories implementation will still dependent on IDataContext. But for me it will help to do TDD more smoothly regardless of my underlying data access layer. Beside it might allow me in future to be able to switch from EF to LINQ to SQL and just implement my IDataContext interface for LINQ to SQL.