Tfs2012 improvements are mainly reflected in the following aspects:
Directory
TFS user manual... 1
1. Connect and use TFs. 2
How to connect to team Foundation server. 2
Create a team project... 3
Add members to the team... 3
2. Add source code to version control... 4
Add source code to version control... 5
Connect to the team Foundation server and obtain the file... 5
3. Backlog management... 6
Backlog during project creation... 6
Changing projects takes precedence over backlog... 7
Record estimated workload and business value... 7
Determine the team capacity for this iteration... 8
Input team capacity data... 9
Create a task... 9
4. Test backlog of work items... 11
Connect to the Team Project... 11
Create a test plan... 12
Add details to the test plan... 13
View product backlog items... 14
Start the exploration test session... 15
To add comments, screen snapshots and file attachments will be added during the exploration test session... 16
To report bugs and test sessions during discovery... 18
To create a test session during test case exploration... 20
Tracking progress exploration test... 22
5. Work item and code review... 23
Check my work... 23
Code review... 24
6. Context Overview (interface design diagram and description)... 25
Use the PowerPoint to design the user interface... 25
7. customer feedback... 27
8. Manage the project documentation... 27
Visual Studio team Foundation server 2012 (TFS) is the core collaboration platform for Microsoft Application lifecycle management (ALM) solutions. Both locally and in the cloud, TFS supports flexible development practices, multiple IDES and platforms, and provides you with the tools required to effectively manage software development projects throughout the IT lifecycle.
The link below is TFsVideo:
Http://channel9.msdn.com/Series/Visual-Studio-2012-Premium-and-Ultimate-Overview-CHS/Visual-Studio-Ultimate-2012-Coordinate-your-team-with-agile-project-management-CHS
Install team Foundation server (TFS)Create a team project, add team members to the project, and place the code in the project under version control. Therefore, the team can obtain the TFS.
Note:
· Some functions may be unavailable. Based on the permissions or versions of the team Foundation server. For more information, see accessing through "Web Permissions.
1. How to connect to and use TFs to connect to the team Foundation Server1. Run Vs and open or select the team resource manager.
2. on the home page, select connect to team Foundation server.
3. In the connection to the Team Project, select the server.
4. In Add/delete team Foundation server, select Add to open add team Foundation server.
5. For the name or URL of the team Foundation server, specify your server name (10.0.103.93), select OK, and disable.
6. After you connect to the team Foundation server, open the Select Team Foundation Server LIST and select the server and connection to be added.
Create Team ProjectTo create a team project, please send an email to [email protected]
Add members to the team1. on the team web access homepage (http: // 10.0.103.93: 8080/TFS), select a team project.
2. Under members, select Manage members.
3. On the XX team member management page, open the Add list and select Add Windows user or group.
4. Add a Windows user or group and enter the alias (domain \ alias) for each team member. For example:
2. Add source code to Version ControlAfter the Administrator uploads the Code project to the version control repository, the team members can obtain the TFS code. The team connects to the Team Project and downloads the code to add it to the development computer to start the work.
Description |
If your team works in multiple versions at the same time, you can create branches for each version. In a large organization, you can create a branch of each function so that the team can be organized in comparison to isolation, normal, and mutual integration. |
1. Open or select the team resource manager.
2. Under pending changes, select Source Code Management Resource Manager.
3. At the top of the source code management resource manager, select the local path not mapped.
4. In ing, enter the full path of the folder on the computer that contains the project code, and then select ing.
5. In Solution Explorer, open the shortcut menu at the top of the solution and add the solution to source code management.
6. In the team resource manager, choose to suspend the change.
7. Under the comment, enter the comment in, and then select register.
Connect to the team Foundation server and obtain the file1. Connect to the Team Project.
2. Open the source code management resource manager.
3. Map the root folder of the version control repository to the folder on the local computer on which the code is to be retained.
4. In the source code management resource manager, open the shortcut menu of the project and select get the latest version.
3. Backlog ManagementThe team can manage their backlog in TFs. Add backlog items to team projects. When team members plan the next iteration, they use the backlog work page to identify the iterations backlog work items and break them into tasks. You can use team web access to create a backlog, or use Visual Studio or team explorer to manage the backlog.
Backlog during project Creation1. on the homepage, under the activity, select View backlog.
2. Enter the title of the backlog and select enter.
Changing projects takes precedence over backlog· In the directory, please drag this item to the correct position of the list.
Record estimated workload and Business Value1. Double-click the backlog item. (Keyboard: displays backlog items and selects the Enter key .)
2. Specify the workload ., Business value or two. Save and close the work item.
Determine the team capacity for this iteration1. on the team web access homepage (http: // almsvr: 8080/TFS), select the Team Project (fabrikamfiber ).
2. Under the activity, select View backlog.
3. In the backlog pane, under the current, select the current iteration (sprint 1 ).
4. In the main pane, select capacity.
Input team capacity data1. In the Reach pane, type the hours in the typical day of the week to work for each team member.
2. For each team member who needs one or more rest days, select and enter the number of rest days.
Prompt |
During the iteration of the Plan, the team's work is assigned to individuals. If your team has assigned a task, you can use the team to determine the team and no more work can be done in the iteration. If each team member executes only one type of activity (such as development or testing), the event of each team member on the Capacity page can be monitored by the event team capacity. |
The first item is allocated to the current iteration (sprint 1) for the backlog of products with the highest priority ). The team discusses each task to complete the backlog and creates a task work item for each task. The Team estimates the hours required for each task. Add tasks to backlog items, assign them to users who will execute them, and record estimates.
After the team is created, it is estimated that a task is assigned to the first backlog and the team capacity is checked. Therefore, the Team continues the next process of the product backlog, until the team capacity is disabled.
1. In the backlog, select the product backlog.
2. Drag a product backlog from the list to the backlog pane and place it in iteration (sprint 1 ).
3. In the backlog, select iteration (sprint 1 ).
4. In the directory, select.
5. Enter the task title near the top of the work item form.
6. Open the assignment to the list and select the person who will complete the task.
7. For the remaining work, enter the estimated end hours of the task.
4. Test the backlog of work items to connect to the Team Project1. After Visual Studio 2012 is installed, you can see it in the Start Menu.Microsoft test Manager, OpenMicrosoft test Manager.
2. If you want to add a server running team Foundation server (TFS), enter its name or URL in the box and select Add (consistent with the preceding TFs connection ).
3. After connecting to a team project, under the team project set, expand the team in the project list and select your team project. (For example, fabrikamfiber ).
4. Select connect now.
Create test plan1. In the test center, select Add.
2. When you add a test plan,Sprint 1), And select Add. The plan is now listed in the test plan.
Prompt |
You can create other team members to use the URL to access this plan. Copy the URL of the URL plan you created to the clipboard by selecting the copy plan. You can now paste this URL into an email and send it to other Members in the team, so you can easily access the plan. See how to: Use a URL to switch between test plans. |
3. Select a test plan from the list. Select a plan to open the Microsoft test Manager and display the content view test plan.
Add details to the test plan· To view the attributes of a test plan, select attributes.
· To route the test plan to different iterations, select iteration and iteration (for example, fabrikamfiber \ release1 \ sprint1 ).
Description |
When a test plan is added to an iteration, the Resource Manager tab of the test case shows only backlog items allocated to the iteration. |
1. on the menu bar, select test.
2. Select to execute the exploration test to open the browsing window and view all the backlog work items and test plans.
Description |
The list includes all work items in the required category. |
3. Select the product backlog to open.
4. Before running the test, open the project and add details.
Start the exploration test session1. Select the backlog of products to perform the exploration test.
2. Select test work item to open the exploration test window.
Description |
To specify the test settings for generating or rewriting the test plan, and set the environment, select use option to browse. See how to: override the settings that apply to test run in the test plan. |
3. Select Start to start the record.
4. Start the application to be tested.
Open a browser and test the Customer Portal.
Prompt |
You can pause recording. If you need other tasks, note that when the test session is running. You can perform other operations on your computer, such as responding to emails without including them in this record. See how to: Pause recording during exploration test sessions. |
You can add screen snapshots and comments to help identify bugs and problems in other applications. Displays how Adam adds screen capture and comments when the user views spelling errors.
You can also explore the files in the test window and submit bugs. For example, you can set the requirements for the application or log file generated by the application.
1. In the exploration test window, on the toolbar, select capture rectangular screen snapshot (camera icon ).
The exploration test window disappears and the pointer changes to a cross line.
Prompt |
(Optional) open the list of captured rectangular screen snapshots, and select capture full screen snapshots or get window screen snapshots. |
2. Draw a selection box around the area of the screen to capture.
The comment box in the exploration test window now contains the screen snapshots for the selected area.
3. To add comments, enter their exploration test window in the comments.
Prompt |
To set the comment text, use the exploration test window in the comment toolbar. By using the format setting options (bold, underline, or color display, you can click the key. To add a file, select an additional file (the paper clip icon) in the toolbar of the exploration test window ). Specify a file, such as a requirement or log file, which is appended to the test and appears in a window of the exploration test. |
1. on the toolbar of the exploration test window, select create bug.
Create a new bug form with comments, screen snapshots, file attachments, and audio and video recording displayed in the steps to be reproduced.
Description |
When a bug is created, the exploration test window is automatically paused. |
2. In the title, type the title of the bug.
3. Open the assigned to list, and select a team member for further investigation to assign the bug.
4. to view information about the computer used for testing, select system.
5. to update the severity level of a bug, open the Severity Level list and select severity level.
6. To view the test result attachment, select the attachment.
7. To change the operation steps in the bug, select the Change step.
8. The selection steps are included in the bug.
9. Click Save and close.
Prompt |
Create a manual test step-based use case log on to your session, select save and create a test. This will create a link between bugs and manual test cases. Applies to any changes made one by selecting the Change step. The next process describes how to create a manual test during a session. |
10. Restore the record in the exploration test window and add a new bug pointing to the comment box. You can continue your session and create other defects.
Description |
The bug you created is also displayed under the bug node. The bottom of the exploration test window is near. If you select the link to explore the test window in the comments or on the bug node, You can edit the bug. See how to: View bugs previously submitted during the exploration test session. |
11. For how to use team resource manager and Visual Studio to fix this bug, see develop code for backlog items and fix the bug.
To create a test session during test case ExplorationYou can create a manual test based on the use of the exploration test window. The steps you record during your session are automatically case sensitive. If you create such a test case, it is associated with your backlog and placed in the corresponding test suite. All bugs. Documents during this meeting have the same project automatic link and manual test cases associated with the Team Project. In this way, you can divide test cases into multiple identical test suites or other test plans. You can also narrow down test cases and use them to test applications in the future. See how to: create a manual test case from the exploration test session, create a manual test case, and run a manual test using the test run program.
1. In the toolbar of the exploration test window, select create test case.
Display new test cases. This includes the steps you perform during the exploration test.
Description |
When you create a manual test case, the record in the exploration test window is automatically paused. |
2. Enter the title here and the title of the new test case.
3. Edit other fields in the test case as needed.
For example, select priority and assign to value.
4. To change the operation or expected results, go to step options and edit the information in the operation and expected results columns.
For example, you can insert additional steps and share steps. See create manual test cases and how: share common test cases with sharing steps.
5. select Save and close.
In the exploration test window, restore the record to explore the test session and add the situation that points to the new test in the comment box. The test cases are also displayed under the test case node. The bottom of the exploration test window is near.
Prompt |
To edit a test case, select the link to explore the test in the comments window or under the test case node. |
You can continue your sessions and create other bugs and test cases.
Tracking progress exploration test1. to view your progress, select the test and test sessions you want to view.
2. Select "open ".
The session details are displayed.
5. Check my work for work items and code reviews1. Open vs'sTeam Resource Manager, SelectMy work.
Code ReviewCode review can improve code quality.
1. Open vs'sTeam Resource Manager, SelectMy workUnderRequest Code Review.
2. Select the name of the reviewer, enter the subject and description, and clickSubmit request.
6. use PowerPoint to design the user interface.After Visual Studio 2012 is installed, you can findPowerPoint storyboarding(PowerPoint demo ). You can quickly declare a user scenario or declare this purpose in a work item using a PowerPoint presentation. Format text and insert an image directly. A visual team that provides content needs to generate feedback that allows you to easily obtain feedback from your team and stakeholders.
You can use a PowerPoint Board to present a presentation to the customer or provide feedback to the development team. The demo image can be linked to the backlog of work items.
1. Open the PowerPoint.
2. design the interface (you can drag the background and control model, for example, to design a SharePoint Portal, you can selectSharePointAnd then modify the interface ).
7. Customer FeedbackAfter Visual Studio 2012 is installed, you can see the following tools:MicrosoftFeedback Client
On the Microsoft feedback client, stakeholders can use work software to directly interact and record richer and more operable data. Data is automatically stored as comments, screen snapshots, and videos or recordings in the background. For details, click the following link:
Request and process stakeholder feedback
Provide feedback
8. Manage project documentsProject document page validity is only valid when the project portal and SharePoint website are enabled for the Team Project. Team members can view them by double-clicking the document. You can also upload, delete, move documents, libraries, and folders, and execute other tasks on documents, libraries, and folders.
Project members can use Visual Studio's team resource manager, team web access, or project portal to manage documents and document libraries. For example:
Source: http://www.cnblogs.com/codelove/
The copyright of this article is shared by the author and the blog Park. You are welcome to repost this article. However, you must retain this statement without the author's consent and provide a clear link to the original article on the article page. Otherwise, you will be held legally liable.
Listen to the flowers and flowers, and enjoy the cloud.
Start building with 50+ products and up to 12 months usage for Elastic Compute Service
1 on 1 presale consultation
24/7 Technical Support 6 Free Tickets per Quarter Faster Response
Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.
A comprehensive suite of global cloud computing services to power your business
Payment Methods We Support
