.NET news » Testing 
Creating UI Automation Client Applications
Sometimes an application needs to interact with the user interface (UI) of a second application. The first application might be a test application that drives the UI of the target to run through some automated tests. It might describe the UI out loud, as an aid to users that are blind. It might be a speech application that allows users to give vocal commands. In each of these cases, the application needs a way to inspect and interact with the UI of the system and other running applications.
NCover Basics: Improving Json.NET's Test Suite with NUnit and NCoverExplorer
Using MVC to Unit Test WPF Applications
Musings on Software Testing
Improving Application Quality Using Test-Driven Development (TDD)
Three Ways to Implement Dependency Injection in .NET Applications
The dependency injection pattern, also knows as Inversion of Control, is one of the most popular design paradigms today. It facilitates the design and implementation of loosely coupled, reusable, and testable objects in your software designs by removing dependencies that often inhibit reuse. Dependency injection can help you design your applications so that the architecture links the components rather than the components linking themselves.
This article presents an overview of the dependency injection pattern, the advantages of using dependency injection in your designs, the different types of dependency injection, and the pros and cons of each of these types, with code examples where appropriate.
Monitor .NET Code Quality with FxCop and Custom Rules
Ranorex - free GUI test and automation library for C++, Python and all .NET languages
Improve Code Quality with Unit Testing in Visual Studio Team Edition
Device Security Manager Powertoy for Windows Mobile 5.0 Released!
This test tool helps developers of Windows Mobile applications test various security policies for Windows Mobile devices.
It is designed as a desktop application that ships with a preset list of "security configurations". A security configuration can be thought of as a template, which contains a collection of individual policies and settings. For example, a security configuration could define policies such as whether unsigned applications are allowed to execute, whether RAPI is disabled etc. Using this tool, the developer can provision a Windows Mobile device with different configurations, and then test the application's behavior under these configurations. This tool can be used either on an emulator or an unlocked Windows Mobile device.

