Tulsa TechFest 2010 - What's New in TFS 2010

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 slide is available as a comparison if you want to compare/contrast with the 2010 slide.It’s also nice to be able to tell the VSTS 2008 story before diving into what’s new in 2010.
3. This is the fully animated slide.
4. 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”
5. MMC applicationCover in a little more detail during demos.
6. Can be supported by TFS 2008 and 2010
7. Scalability at every level in TFS 2010
8. Demo branch visualization
9. 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.
10. 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.Gated Check-in - CAN BE BYPASSED with permissions
11. Hierarchy handled via multiple “Title” columns in Excel – one for each level
12. You can now create multiple levels of custom query folders
13. 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
14. You start by using a work item query
15. 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.
16. This gives you a good start based on a query you understand, reports to break down current state and trend, and allow customization.
17. Information relevant to userCan be customized like any other SharePoint site
18. Information relevant to overall project
19. 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)
20. http://blogs.msdn.com/mathew_aniyan
21. Test the Windows Calculator app to verify that 7+2=9.Create a new Coded UI Test.Selected “Record Actions…” option from the “Generate Code…” UI.The Coded UI Test Builder will appear.Launch calc.exePress the Record button on the Coded UI Test Builder.Click 7 + 2 =Notice the keystrokes are recorded in the Recorded Action dialogClick the Generate Code button on the Coded UI Test Builder.Give the test a name such as “TestAdd” Now we need verify the sum is correct, so click on the result field using the Coded UI Test Builder crosshairProperties of the selected control are shown in the Coded UI Test Builder Window. Right click on the Display Text field and choose Add Assertion. In the Add assertion for DisplayText dialog, click OK. Click on the Generate Code Button and change the Method Name to AssertSum. VS will display the Coded UI test Execute the test from VS test runner and view the results.
22. http://blogs.msdn.com/gautamg/archive/2010/01/07/platform-support-for-coded-ui-test-and-fast-forward-feature-of-test-runner.aspx