Visual Studio Test Tooling Guides

Updated Wiki: Home

wschaub — Thu, 09 May 2013 22:58:10 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

This guidance is created by the Visual Studio ALM Rangers, who have the mission to provide out of band solutions for missing features and/or guidance. This content was created with support from Microsoft Product Group, members of Microsoft Services, Microsoft Most Valued Professionals (MVPs) and technical specialists from technology communities around the globe, giving you a real-world view from the field, where the technology has been tested and used.

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

Team
Adimulam Sudheer, Anutthara Bharadwaj, Brian Blackman, Casey O'Mara, Cesar Solis Brito, Christofer Löf, Harish Reddy Kothapalli, Hassan Fadili, Mathew Aniyan, Ravi Shanker, Richard Albrecht, Richard Fennell, Tim Star, Tony Whitter

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://aka.ms/vsarunderstand.

Feedback

Post comments on the Discussions Page.

New Post: Fakes - Compilation DisableCodeContracts="true"

mikeFourie — Thu, 25 Apr 2013 20:52:54 GMT

Something to add to a 2nd edition --- http://social.msdn.microsoft.com/Forums/en-US/codecontracts/thread/93b6830f-0898-40c2-a4f4-678faeb9aa4f

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 20:04:06 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 20:02:42 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 20:01:49 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Release: v1.0 - DevOps bug resolution using IntelliTrace (Apr 11, 2013)

wschaub — Fri, 12 Apr 2013 19:58:35 GMT

Welcome to the end to end guidance for DevOps bug resolution using IntelliTrace

Quality-Bar Details

Documentation has been reviewed by Visual Studio ALM Rangers
All critical bugs have been resolved

Known Issues / Bugs

None

Released: v1.0 - DevOps bug resolution using IntelliTrace (Apr 11, 2013)

Fri, 12 Apr 2013 19:58:35 GMT

Welcome to the end to end guidance for DevOps bug resolution using IntelliTrace

Quality-Bar Details

Documentation has been reviewed by Visual Studio ALM Rangers
All critical bugs have been resolved

Known Issues / Bugs

None

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 16:45:11 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Release: v1.0 - DevOps bug resolution using IntelliTrace (Apr 11, 2013)

wschaub — Fri, 12 Apr 2013 05:25:38 GMT

Welcome to the end to end guidance for DevOps bug resolution using IntelliTrace

Quality-Bar Details

Documentation has been reviewed by Visual Studio ALM Rangers
All critical bugs have been resolved

Known Issues / Bugs

None

Released: v1.0 - DevOps bug resolution using IntelliTrace (Apr 11, 2013)

Fri, 12 Apr 2013 05:25:38 GMT

Welcome to the end to end guidance for DevOps bug resolution using IntelliTrace

Quality-Bar Details

Documentation has been reviewed by Visual Studio ALM Rangers
All critical bugs have been resolved

Known Issues / Bugs

None

Updated Release: v1.0 - DevOps bug resolution using IntelliTrace (Apr 11, 2013)

wschaub — Fri, 12 Apr 2013 05:25:02 GMT

Welcome to the end to end guidance for DevOps bug resolution using IntelliTrace

Quality-Bar Details

Documentation has been reviewed by Visual Studio ALM Rangers
All critical bugs have been resolved

Known Issues / Bugs

None

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 05:24:26 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 05:24:00 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 04:48:34 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Team
Larry Guger (product owner), Tony Whitter (project lead) and Anna Galaeva, Brian Blackman, Casey O'Mara, Giulio Vian, Jesse Houwing, Marcel de Vries, Mathias Olausson, Mike Douglas and Vlatko Ivanovski
Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

Updated Wiki: Home

wschaub — Fri, 12 Apr 2013 04:47:26 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

DevOps bug resolution using IntelliTrace

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

New Post: Fakes - increase logging for vstest.console.exe

mikeFourie — Wed, 10 Apr 2013 08:29:41 GMT

Here's a handy link for increasing logging if you are having issues with vstest.console.exe

http://blogs.msdn.com/b/aseemb/archive/2012/03/02/how-to-enable-ute-logs.aspx

Updated Wiki: Home

wschaub — Tue, 09 Apr 2013 20:14:42 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

IntelliTrace (COMING SOON)

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

The guidance includes the following artefacts:

Cheatsheet - Build Master DevOps and IntelliTrace Checklist
Cheatsheet - IntelliTrace Cheat Sheet
Cheatsheet - Ops view of DevOps and IntelliTrace
Hands-on Lab - Build (Symbols Configuration & Build)
Hands-on Lab - Dev (Client Side No Symbols Found Resolution)
Hands-on Lab - Ops (Collection for WPF Rich Client)
Poster - Encountering IntelliTrace technology in DevOps
Poster - Resolving bugs in DevOps with the help of IntelliTrace
Quick Reference Guide - Developer view of DevOps and IntelliTrace

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.

New Post: Support for WinRT & WP8

wschaub — Tue, 12 Mar 2013 18:39:09 GMT

At this stage this team is not aware of any timescales or estimations for Fakes support of Windows Phone 8 or Windows store apps. As soon as we have news on this topic and future updates of the guide, we will share them on http://vsartesttoolingguide.codeplex.com and http://blogs.msdn.com/b/willy-peter_schaub.

New Post: Support for WinRT & WP8

Sledge70 — Tue, 12 Mar 2013 17:50:50 GMT

Any idea of timescales for supporting fakes Windows Phone 8 & Windows store apps?

*S

Updated Wiki: Home

wschaub — Fri, 08 Mar 2013 20:52:08 GMT

Project Description

This umbrella project delivers a range of practical and scenario based guidance for Visual Studio test features, such as Coded UI , Microsoft Test Manager, IntelliTrace and Microsoft Fakes.

Visual Studio ALM Rangers

What is included in the downloads?

The solutions typically consist of a combination of these deliverables:

Guidance contains scenario based practical guidance, frequently asked questions and quick reference posters.
Hands-on Lab contains the HOL that provides a walkthrough of the planning, based on the guidance

Solutions

Coded UI Guide

Gives you practical answers to questions such as “where in the SDLC should you think about Coded UI Tests”, “ how should you design your Coded UI Tests so that they are maintainable”, “how should you structure your test projects so that large teams can work on them” and “ what are the best practices while building Coded UI Tests”.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the Tester, how to best manage Coded UI in the SDLC process.
As Christine, the Tester, how can I share Coded UI Tests for shared UI components across projects and teams.

Also refer to the Visual Studio Coded UI Microsoft Word Plug-in, which extends the Coded UI feature support to Microsoft Word documents.

IntelliTrace (COMING SOON)

Supplements the Test Tooling Guide with the DevOps end-end scenario, giving you access to ALM end to end labs and guidance that include bug resolution using IntelliTrace.

The Epics included in the guidance are:

As Bill, the ALM Ranger, I would love practical and exciting DevOps & IntelliTrace Posters.
As Abu the Build Master, I would like practical guidance on how to to configure my TFS Build server to support IntelliTrace.
As Doris, the Developer, I would like practical guidance to resolve a bug in DevOps using IntelliTrace.
As Jane, the Infrastructure specialist, I would like practical guidance to implement IntelliTrace in DevOps.

Also refer to Visual Studio 2012 Application Lifecycle Management Virtual Machine and Hands-on-Labs / Demo Scripts (http://aka.ms/treasure99) for additional Hands-on labs.

Better Unit Testing with Microsoft Fakes

This eBook contains practical guidance for migrating to and unit testing with Microsoft Fakes. Practical walk-throughs allow you to navigate basic and advanced concepts, giving you a comfortable and confident start in implementing Microsoft Fakes as a mocking solution.

The Epics included in the guidance are:

As Doris, the Developer, I would like practical guidance to migrate to the Fakes framework.
As Doris, the developer, I would like practical guidance to understand and implement the Fakes framework within Visual Studio.

Team
Brian Blackman, Carsten Duellmann, Dan Marzolini, Darren Rich, David V. Corbin, Hamid Shahid, Hosam Kamel, Jakob Ehn, Joshua Weber, Mehmet Aras, Mike Fourie, Patricia Wagner, Peter Provost, Richard Albrecht, Richard Fennell, Rob Jarratt, Shawn Cicoria, Waldyr Felix, Willy-Peter Schaub
Foreword

For modern development teams, the value of effective and efficient unit testing is something everyone can agree on. Fast, reliable, automated tests that enable developers to verify that their code does what they think it should, add significantly to overall code quality. Creating good, effective unit tests is harder than it seems though. A good unit test is like a good scientific experiment: it isolates as many variables as possible (these are called control variables) and then validates or rejects a specific hypothesis about what happens when the one variable (the independent variable) changes.

Creating code that allows for this kind of isolation puts strain on the design, idioms, and patterns used by developers. In some cases, the code is designed so that isolating one component from another is easy. However, in most other cases, achieving this isolation is very difficult. Often, it’s so difficult that, for many developers, it is unachievable.

First included in Visual Studio 2012, Microsoft Fakes helps you — our developers — cross this gap. It makes it easier and faster to create well-isolated unit tests when you do have systems that are “testable,” letting you focus on writing good tests and not on test plumbing. It also enables you to isolate and test code that is not traditionally easy to test, by using a technology called Shims. Shims use runtime interception to let you detour around challenging dependencies and replace them with something you can control. As we have mentioned, being able to create this control variable is imperative when creating high-quality, fast-running unit tests.

Shims provide a very powerful capability that will let you circumvent all kinds of roadblocks when unit testing your code. As with all powerful tools, there are a number of patterns, techniques and other “gotchas” that can take time to learn. This guidance document provides you with a jump-start on acquiring that knowledge by sharing a large number of examples and techniques for effectively using Microsoft Fakes in your projects.

We are happy to introduce this excellent guidance document produced by the Visual Studio ALM Rangers. We are sure that it will help you and your team realize the power and capabilities Microsoft Fakes provides you in creating better unit tests and better code.

Peter Provost – Program Manager Lead, Visual Studio ALM Tools

Joshua Weber – Program Manager, Visual Studio ALM Tools

Microsoft Test Manager Guide

Provides guidance on how to use the test impact analysis scenario to get to the set of recommended tests. The scenarios are described in an easy to follow how-to style with detailed illustrations and snapshots to take you through the workflow.

Bookmark the Visual Studio ALM Rangers blog, using tag VSCUG for the latest information on this project.
The Epics included in the guidance are:

As Christine, the tester, how to best use manual testing and test impact analysis.

External References

None

How to submit new ideas?

The recommended method is to post ideas to the Discussions Page or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Feedback

Post comments on the Discussions Page.