Identify the Test Impact in VSTS 2010

As developers make changes to code, it’s critical for them to effectively test their changes – not only to prove the new code work, but to ensure there’s no unexpected downstream effect. Test impact analysis and test prioritization identify the tests that must be run to validate the code changes. This helps developers quickly check-in code with confidence by running only the necessary tests and reduces churn created by unexpected failures.
The new Test Impact View window enables a developer to view a list of tests that need to be run as the result of a code change. The developer can toggle between an Impacted Tests view and a Code Changes view.
• The Impacted Tests view provides a list of tests that need to be
run and which code changes are covered by each of the tests.
• The Code Changes view provides a list of code changes and which tests must be run in order to validate each of them.

These two views provide a easy way to discover what tests must be run in order to validate the changes to the code base without having to run all of the tests. This ensures that all changes are tested effectively.

Eliminating “No-Repro” Bugs in VSTS 2010

From designing an application through developing code, finding bugs that can’t be reproduced is a common problem – the “no-repro” bug. Many factors drive these types of bugs, and we’ve worked to create tools to help isolate the issue and enable faster fixes.
One way this is solved in Visual Studio Team System 2010 is with the use of a tool that can specify the exact state of the build used by a tester and allow a comparison to the state of the build used by the developer when trying to reproduce the bug. It is often the subtle differences between these two that create the no-repro state, and a new tool within Visual Studio Team System 2010 has been designed to specifically address this.
This tool – the Microsoft Test Runner – is a standalone tool that a tester uses to guide them through a series of steps to complete a test case. When the test case is started the Microsoft Test Runner takes a snapshot of the system data, including OS version and Service Pack and other pertinent system data. As the test is being run the tester can use the tool to capture images of the application under test, or even partial or full screen video of the test being run. If an issue is discovered, the tester can create a new bug in Team Foundation Server and attach these artifacts. When attached, the screen capture video is fully indexed with the test steps as bookmarks, making it easier for the developer to see what went wrong on the tester’s machine. All of these artifacts help to eliminate the no-repro scenario, and help build a better bridge between development and test.

Product Overview of VSTS 2010

The marketplace has begun to mature and accept Application Lifecycle Management (ALM) as a proven discipline for creating high-quality applications. However, existing solutions in the marketplace have not kept pace with the changing needs of technical users and the expanding inclusion of non-technical users as part of the lifecycle.
Every customer today faces a similar set of business problems:
• How do we build high quality applications that deliver
real business value?
• How do we embrace the Application Lifecycle Management model effectively?
• How can we ensure that all members of the team – both
technical and non-technical – are part of the process?
• How can we get the most value from our existing code assets?
• How do we make powerful modeling tools available to
everyone in the application lifecycle?
The third generation of Visual Studio Team System – Visual Studio Team System 2010 – will be a robust and streamlined solution that addresses these needs and concerns.
We are evolving Application Lifecycle Management by:
Building quality into the lifecycle
• Ensuring architectural consistency through the lifecycle
• Eliminating “No-Repro” bugs
• Ensuring smooth build handoffs and high quality builds
• Incorporating performance in the lifecycle
Driving efficiency into the test effort
• QA Team aligned with Business Analysts,
Architects, and Developers
• Eliminating tedious tasks
• Improving setup and deployment of tests
• Choosing the right tests
Ensuring Complete Testing
• Focused test planning and progress tracking
• Transparently see the quality of requirements and level of testing
• Finding the gaps in testing and fill them
• Ensuring changes are properly tested

Office Business Application Development in VSTS 2010

Visual Studio 2005 delivered the first release of Visual Studio Tools for Office. Since then Microsoft Office development has become an integrated component of Visual Studio and
as Office moves to deliver a client and server experience so too Visual Studio.
In Visual Studio 2010 developers will be able to build Office client applications that span multiple versions of Office, either 32 or 64-bit and deliver these as a single deployment package. The creation of the deployment packages is assisted through the provision of a deployment design surface that developers can use to graphically assemble the package that the end-user will install. Not only is the creation of the package easier by the ability to leverage “ClickOnce”, CD or Web installs enable developers and IT Professionals to use the appropriate technology to get these applications onto the end user machines.
The task of building the applications themselves has also gotten easier with the introduction of designer support for building flexible UI in either WPF or Fluent. With these designers developers will be able to customize the Office File Menu, Task Panes, Outlook Form Regions and the Fluent UI itself (such as the ribbon view). Additionally the task of consuming data in Office applications is made easier through improved data binding, integration of various Office data sources with LINQ and the ability to data bind to the Business Data Catalog. Finally applications will be able to interoperate with the many Office objects such as lists and action panes, and also participate with the Office Live Viewer.