Getting Started with Automated White Box Testing (and Pex)

Jonathan de Halleux, Nikolai Tillmann

Rate me:

5.00/5 (19 votes)

28 Jan 2009Ms-PL9 min read

126.2K

602

121

Pex is a new tool that helps in understanding the behavior of .NET code, debugging issues, and in creating a test suite that covers all corner cases -- fully automatically.

This article provides a step by step introduction to Pex in Visual Studio 2008 or 2010 CTP. You will learn how to analyze existing code with a few clicks in the code editor, how to create test cases that reproduce issues that Pex finds and debug such issues, how to let Pex generate and save an entire test suite, how to write parameterized unit tests and also why parameterized unit tests will change the way you write unit tests.

Views

Daily Counts

Downloads

Weekly Counts

License

This article, along with any associated source code and files, is licensed under The Microsoft Public License (Ms-PL)

Written By

Jonathan de Halleux

Engineer

United States

Jonathan de Halleux is Civil Engineer in Applied Mathematics. He finished his PhD in 2004 in the rainy country of Belgium. After 2 years in the Common Language Runtime (i.e. .net), he is now working at Microsoft Research on Pex (http://research.microsoft.com/pex).

Written By

Nikolai Tillmann

Software Developer (Senior) Microsoft Research

United States

Nikolai Tillmann is a Principal Research Software Design Engineer at Microsoft Research.

His main area of research is program specification, analysis, testing, and verification. He is leading the Pex project (http://research.microsoft.com/Pex), a framework for runtime verification and automatic test case generation for .NET applications based on parameterized unit testing and dynamic symbolic execution.

Previous projects he worked on include AsmL, an executable modeling language, and the Spec Explorer 2004 model-based testing tool. He contributed to XRT, a concrete/symbolic state exploration engine and software model-checker for .NET code. Spec Explorer 2007 is based on this engine, which is now productized internally by the Protocol Engineering Team at Microsoft to facilitate quality assurance of protocol documentation.

He received his M.S. ("Diplom") in Computer Science from the Technical University of Berlin in 2000.

Getting Started with Automated White Box Testing (and Pex)

Views

Downloads

License

Comments and Discussions