Team Foundation Server Update 2.1 release Log

Microsoft released the visual Studio Team Foundation Server Update 2.1 on May 5, 2016. Let's take a look at the new features that Update2.1 has brought to us.
: Team Foundation Server Update 2.1
Note: Team Foundation Server Update 2.1 Fixes some of the bugs in the previously released Update 2.0, please refer to the following: HTTPS://MSDN.MICROSOFT.COM/EN-US/LIBRARY/6 da268be-c72c-43a5-95ad-9f28c1ef400c

team ProjectCreate, delete, team projects

Administrators can complete the creation and deletion of team projects on the web without having to log on to the TFS server.

figure– Creating a Project

figure– Deleting items

Team Foundation Server Extensions

TFS provides an extended administration page that allows administrators to easily manage the plug-ins used by the current project team. and open up the extension market, you can now put your own development of plug-ins in the market for sale, but also free for everyone to use. The current plug-in market already contains a large number of plugins.

figure– Extension Management

Publishing Features

TFS finally integrates the release functionality into TFS, and the real implementation completes the full application lifecycle management from requirements to delivery on one platform, like!

• In the menu above the TFS Web page, select release for release management, publish features and build a common agent, and by default, share tasks when creating a release pipeline.
• Multiple release pipelines can be configured, multiple triggering methods, including automatic triggering after successful continuous integration

  
  figure– Release Trigger Settings

• Get free plug-ins in TFS Marketpalce to integrate with VMware, SCVMM (System Center virtual machine Manager), Docker and other mainstream virtualization tools for rapid DevOps
• Because you publish and build pooled agents and tasks, you can run tests as needed in the publishing process and display the test results on the release summary page

  
  figure– Publish Summary test results

• Show publishing results in the build summary

  
  figure– publish results in the build summary

instrument panel

This release has made a lot of improvements to dashboards, allowing more content to be displayed on the dashboard and more flexible to configure.

• Dashboard editing mode: Enter edit mode to edit dashboards

  
  figure– edit mode

• Auto Refresh Dashboard: You can now customize a cool dashboard and use the big screen to show where team members can see it, without manual refresh, and automatically refresh every 5 minutes

  
  figure– Automatic refresh Configuration

• A few new widgets have been added to the dashboard: generate results History and pull requests
• You can now add Work item query charts directly to the dashboard

Demand ManagementDelete a work item

You no longer need to use the command line to delete your work items, and TFS provides the removal functionality. Deleted work items are put into the Recycle Bin, and deleted work items can be recovered in the Recycle Bin, and only work items that are purged in the Recycle Bin are completely removed from TFS. And the delete operation has a separate permission option, the administrator can individually configure the delete permission.

figure– Deleting work Items

prioritizing in Kanban for sex

To sort work items while changing columns on the board

figure– Work Item Sort

Management's Gospel: shortcut key Actions

The introduction of shortcut keys greatly simplifies the complexity of operations for managers who frequently work on extrusion pages and boards on TFS

figure– shortcut keys

Source Code Controlversion Control Web

Opening the Code Center gives you a visual view of the basic quality of the current code, which requires the user to configure a build definition with the current branch as the source.

figure– Source Code Quality

Pull request feature elevation

Can now be used in the discussion of pull requests

• Use the @ symbol to remind someone, such as: @WilsonBo, that a reminder will receive an email alert that includes a pull request, a commit, a changeset link
• Use the # symbol to indicate a work item, such as: #22, which can be used in pull request discussions, commits, changesets, and shelveset comments

git branches associated with work items

A new link Type "branch" is added to the work item links. You can create a branch directly on a card in the work item edit form and on the board, and then automatically add a branch link to the work item after the branch is created.

figure– Creating a Branch

figure– Branch Link relationships

A new link type "Pull request" has been added to the work item links. When you create a pull request, the work items in all commits are also included by default, and the Pull request link relationship is included in the link relationship for all associated work items after the pull request is completed.

figure– Pull Request

figure– Work Item Association pull request

Build Management

• Build management. The administrator who builds the queue can now control who can create build and release definitions that use the given queue. This allows the team to have their own build resources within a given account or project collection.
• Historical statistical information. The queue and pool views show historical statistics for the build and release agents. This allows the build administrator to better understand the usage of a given build resource.
• Build interface improvements. We have simplified the interface for creating new build definitions. You can set key information about your resources and queues after you select a template.
• Expands the build results view. By using the extension framework, you can extend the display of custom information in the build results (sometimes called the build summary) view
• Publish the task as an extension. You can use the library to publish build and publish tasks as part of the extension.

Test Managementtesting in the build process

• A number of optimizations have been made to the results of unit tests and unit test coverage, including new failed tests, test charts, etc.
• You can use the run functional tests task to run automated tests during the build process
• The build Summary interface contains the test results interface, which shows all the test results that were run during the build process, including unit tests and test coverage results, automated test results, etc.

  
  figure– test Results

• The Java language is fully supported for the task "Publish test Results" and "Release Code Coverage"

Manual Test

• A test plan filter was added
• Quick access to test suites and sub-suite content
• The test plan can now be deleted.

Web-based testing

You can now implement web-based manual testing, exploratory testing, and more by installing the chrome plugin. You can record voice, video, and other information during testing, and you can save this information to bugs or test cases that were created during the test run.

figure– Web-based testing

Team Foundation Server Update 2.1 release Log