In this episode of 10-4 we look at a new type of test coming in Visual Studio Team System 2010 known as the coded UI test. Coded UI tests can be created to automatically navigate through your application’s UI, which in turn can be used to verify that the paths …
Nikolai Tillmann and Peli de Halleux give a short tutorial on Pex, an automated white box testing tool for .Net. The tutorial is a pair-programming session where they show us how to get started with Pex in Visual Studio, starting from an (untested) piece of C# code: * how to …
Pex is a white-box test generation tool for .NET. Starting from a hand-written parameterized unit test, Pex analyzes the program-under-test to determine relevant test inputs fully automatically. To this end, Pex executes the program multiple times with different inputs while monitoring the taken execution paths. Pex uses a constraint solver …
Sam Guckenheimer has been the chief customer advocate for VSTS, responsible for its end-to-end external design. He describes his book, Software Engineering with Microsoft Visual Studio Team System, as a framework for thinking about software projects in a way that can be directly tooled by VSTS. It presents essential theory …
In this screencast we will demonstrate how to use the Object Builder pattern to create and setup objects for tests. In the first part we discussed how to introduce the base class for the unit tests to improve readability and cleanness of code. http://highoncoding.com/Articles/443_Refactoring_Unit_Tests_Part_2_Using_Object_Builder_Pattern.aspx
In this screencast we will refactor unit tests to make it more readable. It is very important that you refactor your unit tests. Unit test code is not part of the production but refactoring them can help you in the long run and will provide benefits when maintaining the application. …
