The document discusses the features and benefits of Team Foundation Server (TFS) 2010, focusing on improving the interaction between developers and testers to enhance the quality assurance process. It outlines tools for test management, automation, and collaboration, including coded UI testing and environment provisioning for streamlined testing procedures. Additionally, the document highlights the integration of various testing capabilities within Visual Studio 2010 to facilitate efficient debugging and reporting.

1. Team Foundation Server 2010Testing WorkshopEd BlankenshipMicrosoft MVP (TFS, Visual Studio ALM, and VSTS)Notion Solutions, Inc.www.notionsolutions.com

2. About Ed BlankenshipMicrosoft MVP of the Year

3. ALM/TFS Consultant at Notion Solutions

4. Live in Charleston, SC

5. Blog: http://edsquared.com

6. Twitter: @EdBlankenship

7. E-Mail: edb@notionsolutions.com

8. Author - Wrox TFS 2010 Book: http://bit.ly/TFS2010BookFrustrations in development teams“my testers are spending too long testing the same thing”“tooling is expensive (time, licenses, people)”“the developers say the defects are useless”“when is my software ready to ship?”“we have a changed requirement, what do I need to test?”“developers and testers work in silos and don’t communicate/speak the same language”3

9. Customer Challenges QA is not aligned with lifecycleDevelopers and testers work in silosQA is not leveraged

10. Goals for 2010 Release - TestingAlign QA with the LifecycleCreate tighter Dev/Test interactionEnable highly leveraged QA teams

11. Visual Studio 2010 Test Capabilitiesspecialistgeneralistcoded ui testunit testingweb performance testtest runnerload testtest case managementvirtual lab managementdata diagnostic adapters (video, action log, event log etc)team foundation server with reporting(bugs, requirements, user stories, source control, build)

12. Visual Studio 2010

13. Test PlanningTest ProcessRequirementRequirementTest WritingRequirementTest AutomationTest ExecutionReport Results

14. Testing FeaturesQA Professional focused interface

15. Work Item based test case management, test planning and status tracking

16. Focused on Requirements

17. Identification of high-priority tests

18. Robust manual testing functionality

19. Test definition

20. User-friendly Manual Test Runner

21. Defect data capture tools

22. Automated user interface testingTesting ToolsTest Planning

23. Test Case Management

24. Test Lab Management

25. Test Recording

26. Test Collectors

27. Automated UI Testing

28. Web Performance Testing or Load Testing

29. Load Testing

30. Generic Tests

31. Ordered Tests

32. Unit Tests11Test Case Management

33. 12Test Case is first class work item in TFSDetailed steps along with expected results

34. 13Data drive a test caseSpecify data in parameter table

35. 14Select common steps and convert to Shared Steps

36. 15Shared Steps allows for common steps to be reused across test cases

37. 16Organize Tests using Static (folder) suite

38. 17Or create new test cases & add to suiteAdd existing Test cases to suite

39. 18Organize Tests using Requirements based suite

40. 19Select requirement and add to plan

41. 20Tests already linked to requirement are added to plan

42. 21Assign tests to team members

43. 22Organize Tests using Query Based (dynamic) suite

44. 23Specify a Query

45. 24Tests matching query are added to suite

46. 25Rich Bug

47. Better Tester / Developer CollaborationAutomatically gathers defect and runtime details

48. Eliminates the “ping pong” effect

49. Eliminates the “No Repro” problem27Select Test Case & click Run

50. 28Microsoft Test Runner starts up

51. 29Mark steps (pass/fail) during testingError free data entry of parameters using CTRL+V

52. 30Mark step as fail – bug found

53. 31Add comment

54. 32Take screenshot

55. 33Take environment snapshot

56. 34Click on Create Bug

57. Data CollectorsAction Recording

58. System Information

59. Event Logs

60. IntelliTrace

61. Test Impact

62. Video Recorder

63. [Custom Data Collector]36Bug Form auto-filled with step results & step attachments

64. 37Indexed Video links

65. 38Data collector logs auto attached

66. 39Exact actions performed for each step

67. 40System Info across all VMs in environment

68. 41Link to test case auto-created

69. 42Just enter Title and save the bug 

70. 43Dev clicks on lvr link & selects connect to snapshot of the environment

71. 44Dev is able to access the snapshot’ed environment via LE viewer

72. IntelliTraceReduces debug “cycling”

73. Start Debug

74. Encounter defect

75. Drop into debugger

76. Move back through execution history to locate defect

77. Historical debug trace enables debugging offline test runs

78. “As you sit in the debugger, being able to move backwards while in the debugger (or attach the execution log to a bug) has to be the killer feature coming up in the entire Visual Studio 2010 release.” -John RobbinsIntelliTrace

79. Test Impact AnalysisIdentifies tests impacted by code changes

80. Significantly reduces test timeCoded UI Testing

81. Coded UI TestingEnables verification of UI functionality.Record test actions and VS will generate the resulting code.Assertions can be added to verify functionality.Like all VS tests, results can be stored in TFS.

82. 50From Test->new test, click Coded UI test, specify test name and project name

83. 51Use existing action recording to generate code

84. 52Specify test case which has action recording and click OK

85. 53Code generated from action recording – datasource as TestCase

86. 54Code generated handles data parameterization

87. 55Invoke Coded UI Test Builder for adding assertions

88. 56Drag cross-hair onto the control you want to add assertions on

89. 57Properties of selected control and its UIMap is shown

90. 58Select property to assert on and right click to add assertion

91. 59Add the assert

92. 60Specify Assert method name and generate code

93. 61Code generated for assert method

94. 62Add solution to source control

95. 63Check-in pending changes

96. 64Go to test case that you want to associate the newly created automation

97. 65Specify test method and click OK; save test case

98. 66Newly automated test case will be picked up by dynamic query based suite and run as part of build-deploy-test workflow

99. Platform Compatibility

100. 68Virtual Environment Provisioning

101. Test Lab BenefitsSimplifies environment setup

102. Simplifies testing multiple configurations

103. Enables reverting to baseline configuration

104. Provides checkpoints to aid defect resolution

105. Improves test hardware utilizationLab Management GoalsVirtualize test lab resources

106. Lower technical requirements for test environment creation

107. Enable environment recreation for defect resolutionTeam Foundation Server (TFS)Hyper-V HostsLibrary SharesLab Management in Visual Studio 2010LS1VM1LS2VM2System Central Virtual Machine Manager (SCVMM)Lab ManagementLSnVMnTest Case ManagementAuomated BuildsWork Item TrackingVersion Control

108. 72Create Virtual Environment from Lab Center

109. 73Specify name and location for environment

110. 74Pick role for VMSelect VM from template library

111. 75Specify capabilities – “Run Tests” ; “Run Workflows” ; “Network Isolation”

112. 76Environment (collection of VMs) created

113. 77Manage snapshots for environmentAccess environment using Lab Environment Viewer

114. Lab Management 2010 Capability/FeaturesVirtual Environments (Hyper-V)Physical environmentsVirtual environments (non Hyper-V e.g. VMWare)Visual Studio 2010 Capability/FeatureTestingRunning unit testsRunning manual testsRunning automated, load, and coded UI testsFiling rich bugs with diagnostic adaptersBuild deploymentAutomated build-deploy-test workflow Environment creation and managementCreate environment from VM templatesStart/stop/snapshot environmentConnect to environment using Environment ViewerClone environments using network isolationSupported out of boxNot supported, but possible with customizationNot Supported N/A

115. 79Automated Build – Deploy - Test

116. 80Create new build workflow

117. 81Provide a name

118. 82Specify Build Controller and output drop folder

119. 83Select LabDefaultTemplate

120. 84Specify workflow settings

121. 85Select environmentRevert to a specific snapshot

122. 86Select build definition to build the application

123. 87Specify deploy scriptsTake snapshot after deployment

124. 88Specify tests to run post deployment

125. 89Detailed Build report

126. ReportingBy Test Plan

127. By Requirement

128. By Automated Build

129. Quality Dashboard

130. Bug Tracking ReportsImproved Quality Reporting

131. Improved Test Reporting

132. Improved Test Reporting

133. Improved Test Reporting

134. Improved Bug Reporting

135. Improved Bug Reporting

136. DashboardsExcel Services ReportsTeam Web AccessSharepoint Web Parts

137. Questions?

138. www.notionsolutions.com