TDC 2010 - VS2010 ALM - What's In It for Me

Editor's Notes

1. Visual Studio 2010 is a BIG release!We will cover most of these features during this talk but will not go into detail with all of them. Please ask questions.
2. This is the fully animated slide.
3. There are now 4 basic products: VS Professional, VS Premium, VS Test Elements, and VS UltimateMSDN subscriptions now come with a full production version of TFS and one CALRetail versions of TFS will be able to be purchases for around $500 + CALsNOTE: “Test Elements” is now known as “Test Professional”
4. Two basic installation steps:Install the “bits”Configure the options accordingly
5. Note that options may vary based on the type of operating system TFS is being installed on.
6. Note that I don’t like this screen because, at a quick glance, it makes me think it’s some type of error screen (like you might see in Internet Explorer). Make sure you pay attention to this screen.
7. Offers “Default” and “Custom” configurationsCan be installed without WSS or Reporting Services even being installedConfiguration utility will be launched after install has completedPre-requisites will be verified up front during configuration – before configuration has been completed
8. Example of readiness checks.
9. Example of readiness checks.
10. Example of readiness checks.
11. Example of readiness checks.
12. Installation, step-by-step
13. Done!
14. MMC applicationCover in a little more detail during demos.
15. Can be supported by TFS 2008 and 2010
16. Scalability at every level in TFS 2010
17. Demo branch visualization
18. A branch visualization will be created showing where the change has propagated.Branches shown in green have the fix while branches shown in red do not. Along the top is a timeline showing when the various changesets were checked in.We can track the changes in a timeline view.
19. The Hierarchy View
20. OverviewWhen 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.
21. CAN BE BYPASSED with permissionsOverviewWhen 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.
22. Hierarchy handled via multiple “Title” columns in Excel – one for each level
23. You can now create multiple levels of custom query folders
24. We now support all of excels conditional formatting of cells.We got a lot of feedback that creating ad-hoc reports from TFS is really hard.We have a new feature that enables you to get a quick-start on reporting
25. You start by using a work item query
26. This will launch Excel and give you options on what kind of reports you want to create.This will take the query, parse it, analyze the fields mapping them to the data warehouse, and generate pivot tables and graphs.
27. This gives you a good start based on a query you understand, reports to break down current state and trend, and allow customization.
28. Information relevant to userCan be customized like any other SharePoint site
29. Information relevant to overall project
30. On the server side, lab management is fully integrated with TFS. It uses SCVMM underneath to manage virtual machines. SCVMM provides a virtualization platform agnostic layer as it supports both HyperV and VMware. Lab Management will support only HyperV for 2010 release.
31. There are some minor enhancements, such as support for categories instead of test lists, performance improvements like using more than one core. Simplifying deployment that will result in improved performance as well. Unit Tests can now be extended with custom attributes (like privilege escalation attribute). The unit test type can be extended to provide custom coded tests (this is how coded UI is implemented)