Welcome to MSDN Blogs Sign in | Join | Help

Browse by Tags

All Tags » Component Devel... » Unit Testing   (RSS)
Sorry, but there are no more tags available to filter with.

SqlExpressDatabaseInstaller

When unit testing data access components, I prefer to test against run-time components that match the target environment as closely as possible. In other words, if the data access component targets SQL Server 2008, I prefer to test against a SQL Server

Unit Testing Activity CodeDOM Serializers

Windows Workflow Foundation (WF) defines workflows as object graphs. To save or compile workflow definitions, these object graphs must be serialized, and WF supports serialization to both XAML and code. Similar to other components, WF utilizes the .NET

Validating Code Serialized by CodeDomDesignerLoaders

A while back I wrote about unit testing component serializers , but I left the task of validating the generated code against an expected result up to the reader. The approach outlined in that article was to retrieve the generated code as a string and

A Faster TestTypeResolutionService

In February, I wrote about unit testing CodeDomSerializers , but although it was a good initial attempt, there was room for improvement (as I also described in the article). Back then, my main priority was just to get my unit tests working, so other issues

Towards Unit Testing Component Serializers

When writing complex components or controls, it is sometimes necessary to implement custom CodeDOM serialization of the control. If the code serialization logic is complex, it would be nice if it was possible to unit test this logic. It's not quite as

Unit Testing Control Designers

One of the inherent problems of control development is that it doesn't lend itself easily to unit testing. After all, you are developing a user interface, and it's necessary to validate that it looks as expected. While that's true, more complex control
 
Page view tracker