Book Image

Visual Studio 2010 Best Practices

By : Peter Ritchie
Book Image

Visual Studio 2010 Best Practices

By: Peter Ritchie

Overview of this book

When you are developing on the Microsoft platform, Visual Studio 2010 offers you a range of powerful tools and makes the whole process easier and faster. After learning it, if you are think that you can sit back and relax, you cannot be further away from truth. To beat the crowd, you need to be better than others, learn tips and tricks that other don't know yet. This book is a compilation of the best practices of programming with Visual Studio. Visual Studio 2010 best practices will take you through the practices that you need to master programming with .NET Framework. The book goes on to detail several practices involving many aspects of software development with Visual Studio. These practices include debugging and exception handling and design. It details building and maintaining a recommended practices library and the criteria by which to document recommended practices The book begins with practices on source code control (SCC). It includes different types of SCC and discusses how to choose them based on different scenarios. Advanced syntax in C# is then covered with practices covering generics, iterator methods, lambdas, and closures. The next set of practices focus on deployment as well as creating MSI deployments with Windows Installer XML (WiX)óincluding Windows applications and services. The book then takes you through practices for developing with WCF and Web Service. The software development lifecycle is completed with practices on testing like project structure, naming, and the different types of automated tests. Topics like test coverage, continuous testing and deployment, and mocking are included. Although this book uses Visual Studio as example, you can use these practices with any IDE.
Table of Contents (16 chapters)
Visual Studio 2010 Best Practices
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface

Object-orientation and tests


We've briefly covered the concept of object-orientation with regard to tests. We covered encapsulating context within a test class to be shared amongst test classes. But there's much more to object-oriented design that can be taken advantage of in automated tests.

Each test class is a test fixture. The name of the fixture can focus group a given set of tests. We've seen examples of test fixtures that share setup and how that setup would be extracted into a single method or into the constructor to stay DRY. This concept can be expanded to a subgroup related tests into multiple classes to gain extra clarity through the class name into a base fixture class. If we return to our Class1TestsB example, let's say moving TestMethod1 and TestMethod2 into separate classes gives us the ability to subgroup these tests into an individual class with a more clear class name. We could pull up the setup and teardown into a new base class shown as follows:

[TestClass]
public abstract...