This presentation goes through the full testing experience of Visual Studio 2010 and Team Foundation Server 2010 including using the new Lab Management features in the full testing process.

1. Team Foundation Server 2010 Testing Workshop Ed Blankenship Microsoft MVP (TFS, Visual Studio ALM, and VSTS) Notion Solutions, Inc. www.notionsolutions.com

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

9. Customer Challenges QA is not aligned with lifecycle Developers and testers work in silos QA is not leveraged

10. Goals for 2010 Release - Testing Align QA with the Lifecycle Create tighter Dev/Test interaction Enable highly leveraged QA teams

11. Visual Studio 2010 Test Capabilities specialist generalist coded ui test unit testing web performance test test runner load test test case management virtual lab management data 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 Planning Test Process Requirement Requirement Test Writing Requirement Test Automation Test Execution Report Results

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

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

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

34. 13 Data drive a test case Specify data in parameter table

35. 14 Select common steps and convert to Shared Steps

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

37. 16 Organize Tests using Static (folder) suite

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

39. 18 Organize Tests using Requirements based suite

40. 19 Select requirement and add to plan

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

42. 21 Assign tests to team members

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

44. 23 Specify a Query

45. 24 Tests matching query are added to suite

46. 25 Rich Bug

48. Eliminates the “ping pong” effect

50. 28 Microsoft Test Runner starts up

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

52. 30 Mark step as fail – bug found

53. 31 Add comment

54. 32 Take screenshot

55. 33 Take environment snapshot

56. 34 Click on Create Bug

58. System Information

59. Event Logs

60. IntelliTrace

61. Test Impact

62. Video Recorder

64. 37 Indexed Video links

65. 38 Data collector logs auto attached

66. 39 Exact actions performed for each step

67. 40 System Info across all VMs in environment

68. 41 Link to test case auto-created

69. 42 Just enter Title and save the bug 

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

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

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

81. Coded UI Testing Enables 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. 50 From Test->new test, click Coded UI test, specify test name and project name

83. 51 Use existing action recording to generate code

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

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

86. 54 Code generated handles data parameterization

87. 55 Invoke Coded UI Test Builder for adding assertions

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

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

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

91. 59 Add the assert

92. 60 Specify Assert method name and generate code

93. 61 Code generated for assert method

94. 62 Add solution to source control

95. 63 Check-in pending changes

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

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

98. 66 Newly 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. 68 Virtual Environment Provisioning

102. Simplifies testing multiple configurations

103. Enables reverting to baseline configuration

104. Provides checkpoints to aid defect resolution

106. Lower technical requirements for test environment creation

108. 72 Create Virtual Environment from Lab Center

109. 73 Specify name and location for environment

110. 74 Pick role for VM Select VM from template library

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

112. 76 Environment (collection of VMs) created

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

114. Lab Management 2010 Capability/Features Virtual Environments (Hyper-V) Physical environments Virtual environments (non Hyper-V e.g. VMWare) Visual Studio 2010 Capability/Feature Testing Running unit tests Running manual tests Running automated, load, and coded UI tests Filing rich bugs with diagnostic adapters Build deployment Automated build-deploy-test workflow Environment creation and management Create environment from VM templates Start/stop/snapshot environment Connect to environment using Environment Viewer Clone environments using network isolation Supported out of box Not supported, but possible with customization Not Supported N/A

115. 79 Automated Build – Deploy - Test

116. 80 Create new build workflow

117. 81 Provide a name

118. 82 Specify Build Controller and output drop folder

119. 83 Select LabDefaultTemplate

120. 84 Specify workflow settings

121. 85 Select environment Revert to a specific snapshot

122. 86 Select build definition to build the application

123. 87 Specify deploy scripts Take snapshot after deployment

124. 88 Specify tests to run post deployment

125. 89 Detailed Build report

127. By Requirement

128. By Automated Build

129. Quality Dashboard

131. Improved Test Reporting

132. Improved Test Reporting

133. Improved Test Reporting

134. Improved Bug Reporting

135. Improved Bug Reporting

136. Dashboards Excel Services Reports Team Web Access Sharepoint Web Parts

137. Questions?

138. www.notionsolutions.com