6. Visual Studio Team System Visual Studio Team Architect Visual Studio Team Developer Visual Studio Team Test Visual Studio Team Foundation Process and Architecture Guidance Visual Studio Industry Partners Change Management Work Item Tracking Reporting Project Site Integration Services Project Management Dynamic Code Analyzer Static Code Analyzer Code Profiler Unit Testing Code Coverage Visio and UML Modeling Team Foundation Client (includes CAL) Visual Studio Professional Edition Load Testing Manual Testing Test Case Management Application Designer Logical Infra. Designer Deployment Designer Change Management Work Item Tracking Reporting Class Designer Big Build
8. Example Workflow Work Items are the units of communications within the development team. Business Analyst Project Manager Dev Team Test Operations Change Requests Scenarios Quality of Service Reqs Bugs Tasks Production Errors
46. Visual Studio 2010 SKU Features Visual Studio 2010 Ultimate Visual Studio 2010 Premium Visual Studio 2010 Professional Static Code Analysis Database Deployment Code Metrics Database Unit Testing Test Data Generation Test Impact Analysis UI Test Automation Code Coverage Performance Profiling Database Change Mgmt Web Testing Manual Testing Logical Class Designer Load Testing Test Record & Playback Architecture Explorer Layer Diagram UML Modeling IntelliTrace™ Test Case Management Windows Development Generate from Usage Office Development Cloud Development Customizable IDE Web Development Silverlight Tools SharePoint Development Multi-core Development New WPF Editor
47. Visual Studio 2010 SKU Features Visual Studio Test Elements 2010 Visual Studio Team Foundation Server 2010 Visual Studio Team Lab Management 2010 Manual Testing Test Record & Playback Virtual Env Setup/Tear Down Reporting Team Portal Test Case Management Branch Visualization Version Control Test Case Management Checkpoint Environment Lab Mgmt Config Build Automation Environment from Template Gated Check-in Agile Planning Tools
+On the first slide it’s helpful to talk about the Test tools and how they fit into the broader context of the Visual Studio ALM Platform. +This slide is getting updated soon, so right now it’s acting as a placeholder for the new slide.
Team Foundation Highlight
This slide is an alternate version of the next three combined. If you prefer to talk to all three goals on a single slide, use this. If you prefer to talk to each goal seperately, use the following three slides.
Business Alignment centers on ensuring you are building the right thing for the business need and that it is going to be successful when completed. Features supporting business alignment appear in all aspects of the development process. Examples include: Work item tracking improvements, including support for work breakdown hierarchies and customizable link types that allow queries which include the relationships between different types of work. For example, you’ll be able to query for all requirements linked to a particular test. New project scheduling features that enable better coordination between project management and the rest of the organization. The 2010 release includes dedicated integration with Project Server for enterprise wide project management. Additionally you can expect new features for Agile project including more integration with Excel. Dashboards and cross project reports that provide roll up of status across diverse projects with drill down capabilities to investigate hot spots in the data. A simplified data warehouse and reporting experience that makes it easier to build custom reports that fit exactly the questions you want to answer.
Work item tracking improvements, including support for work breakdown hierarchies and customizable link types that allow queries which include the relationships between different types of work. For example, you’ll be able to query for all requirements linked to a particular test. New project scheduling features that enable better coordination between project management and the rest of the organization. The 2010 release includes dedicated integration with Project Server for enterprise wide project management. Additionally you can expect new features for Agile project including more integration with Excel. Dashboards and cross project reports that provide roll up of status across diverse projects with drill down capabilities to investigate hot spots in the data. A simplified data warehouse and reporting experience that makes it easier to build custom reports that fit exactly the questions you want to answer.
Overview When you’re building software as a team, there’s a natural cycle that you follow – testers find bugs, developers fix bugs, testers verify fixes. In order for this cycle to be productive, testers need builds that include fixes to the bugs that the developers have fixed. If the build is broken, there is a risk of holding up the entire team until it is fixed. Gated check-in provides a way to prevent build breaks by validating a developer’s changes prior to committing them to the version control repository. Those changes are validated via an automated build. If the build fails, the user’s pending changes are rejected and passed back to them as a shelveset, otherwise the changes are committed to the repository. Shelve-and-build, a related feature, lets the developer validate their changes with a private automated build. Unlike gated check-in, shelve-and-build is something the developer can choose to do. It can help identify breaks in code that the developer may not generally build on their local machine. Value Proposition If a single developer on your team typically breaks the build just once a year and you have 52 developers working on your project, the build could be broken every week. If you have 260 developers, the build could be broken every day. When the build breaks, the entire team may be stalled resulting in substantial productivity losses. Those losses could be prevented by the gated check-in feature.
+Here we describe the breadth of the testing tools available from Microsoft and how quality is integrated into the end to end lifecycle through TFS. +We achieve integration by ensuring the linkages between requirements, dev, test, defect tracking, change mgmt, etc. +It also sets the stage for the flow of our deck, which starts with Test Planning and moves through the lifecycle and ends with Test Analysis or Reporting. +We can also discuss the goal of VSTS 2010 in democratizing ALM. +We accomplish this by making the tools affordable, and addressing the generalist tester segment that constitutes about 70-80% of the testers today. First, talk about the quality capabilities in each phase of the life cycle. For example, requirements traceability to test cases, defects, source code, development quality attributes such as profiling/tracing, architecture models and layer diagrams, test impact and historical debugging. For test, we'll have it's own section, and then something similar for deploy/maintainance.
We have to understand the types of testers and who we are targeting with these tools. We’ve had specialist testing tools in the past and have improved on them. However the big leap with Test Elements is the support for the generalist tester.
+In General, Manual Testing is supported by the Microsoft Test and Lab Manager that is included in Visual Studio Test Elements 2010 and Specialist testing is supported by Visual Studio.
Microsoft Visual Studio 2010 Professional is the essential tool for basic development tasks to allow developers to implement their ideas easily. This includes core capabilities for Windows, Web, and Office development, along with new capabilities for Cloud and SharePoint development. There are also new tools for Silverlight and Multi-core development. With Visual Studio 2010 the IDE and editor were refreshed using Microsoft Windows Presentation Foundation. <CLICK> Microsoft Visual Studio 2010 Premium is a complete toolset for developers to deliver scalable, high quality applications. This includes support for offline database development, unit testing and change management, static code analysis, performance profiling and code coverage and code metrics. New capabilities including UI test automation (aka Coded UI Tests) and Test Impact Analysis are available in premium. <CLICK> Microsoft Visual Studio 2010 Ultimate is the comprehensive suite of application lifecycle management tools for teams to ensure quality results from design to deployment. This includes IntelliTrace – the new historical debugger which enables debugging events that ran previously on your machine, or another machine. Microsoft Test and Lab manager is included in Ultimate enabling complete Test Case Management and test execution. Additionally the new architecture and modelling tools are included in Ultimate, including support for authoring UML diagrams (Activity, Use Case, Sequence, Component and Class diagrams are supported).
There are some additional products in the Visual Studio 2010 family – Visual Studio Test Elements 2010, Team Foundation Server 2010, and Team Lab Management 2010. Visual Studio Test Elements 2010 is the essential tool for anyone engaging in test case management or manual test execution in the development lifecycle. This tool is designed for the generalist tester – someone who tests applications, but who is not responsible for writing code. This product includes Microsoft Test and Lab Manager (the Visual Studio IDE is not included). Team Foundation Server 2010 is the center of gravity – the hub for a development team. Team Foundation Server has a version control repository, a test case management database, a work item tracking and change management system, support of build automation and a comprehensive reporting solution built on SQL Server Reporting Services. Some of the new capabilities of Team Foundation Server include support for gated check-in, branch visualization and drag-n-drop merge, and new Agile Planning tools. Team Lab Management 2010 enables teams to configure and manage virtual lab environment. Team Lab Management works with System Center Virtual Machine Manage enabling teams to create environment templates, provision ring-fenced environments, and checkpoint those environments. Those checkpoints can be attached to bugs filed using the Test and Lab Manager enabling the person fixing the bug to open the environment right to the appropriate point in the application flow.
![The Microsoft Approach ,[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)