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

Test styles


Testing styles go a long way to making tests readable. Tests help document how the code is used within the system, as well as document certain requirements and acceptance criteria. Test styles help give tests a consistent form and flow so that reading them "flows" and that they are more consistent with one another. Let's go over a couple of well-known testing styles.

Arrange, Act, Assert

Probably the most common test style is Arrange, Act, Assert. This is sometimes referred to as the AAA style. This style of writing separates the code that arranges the variables and state of the test, from the act of operating on the state, from the asserting that the expected state exists at the end of the test.

An example of a test that uses the Arrange, Act, Assert style:

namespace UnitTests
{
[TestClass]
public class Class1Tests
{
[TestMethod]
public void TestMethod1()
{
// Arrange
var o = new Class1();
// Act
var actual = o.Method1();
// Assert
Assert.AreEqual(42, actual);
}
}
}

But, don...