Team Foundation Server 2015 Update 2 Team Foundation Server 2015 Update 2

2016 年 5 月 5 日May 5, 2016

今天,我们非常高兴地宣布正式推出 Visual Studio Team Foundation Server 2015 Update 2。Today, we are happy to announce the availability of the Visual Studio Team Foundation Server 2015 Update 2. 这是最新版本的 Team Foundation Server (TFS),它是 Microsoft 应用程序生命周期管理 (ALM) 解决方案的核心协作平台。This is the newest version of Team Foundation Server (TFS), the collaboration platform at the core of Microsoft's application lifecycle management (ALM) solution.

可以从以下链接安装 Team Foundation Server。You can install Team Foundation Server from the following link.

下载最新版本的 Team Foundation Server UpdateDownload the latest Team Foundation Server Update

请注意:Team Foundation Server 2015 Update 2.1 在 Update 2.0 的基础上修复了一些 bug。Note: Team Foundation Server 2015 Update 2.1 has had some bug fixes since Update 2.0. 请参阅 KB3160281 以查看修复列表。Please refer to KB3160281 for the list of fixes. 对于需要匹配版本的配置(如多应用层),仍可以根据需要下载 Team Foundation Server 2015 Update 2.0If needed, for configurations such as multiple application tiers that require matched versions, you can still download Team Foundation Server 2015 Update 2.0.

若要了解其他相关下载的详细信息,请参阅下载页To learn more about the other related downloads, please see the download page.

欢迎你提供宝贵意见!We welcome your feedback! 如果你有任何疑问,请通过 Visual Studio 中的“发送反馈”选项告知我们。For problems, let us know via the Send Feedback option in Visual Studio. 如有任何建议,请通过 UserVoice 告知我们。For suggestions, let us know through UserVoice.

Team Foundation Server 2015 Update 2 的新增功能What's New in Team Foundation Server 2015 Update 2

功能更新:Feature updates:

改进了团队项目的创建和删除体验 Team project creation and deletion experience improvements

我们将提供在 Web 上通过 REST API 创建和删除团队项目的选项。We're giving you the option to create and delete Team projects from the web experience and through the REST APIs. 这些改进有助于增加 Visual Studio Team Services 和 Team Foundation Server 之间的项目管理操作对等选项。These improvements help to bring more parity between Visual Studio Team Services and Team Foundation Server for project management operations. 有权创建团队项目的用户可以从集合管理视图或导航下拉列表中进行创建。Users who have permission to create team projects can do so from the collection administration view or the navigation drop-down list. 有关详细信息,请参阅 Create a team project(创建团队项目)See creating a team project for more details.

现在可以通过 Web 体验和 REST API 创建和删除团队项目。

同样,有权删除团队项目的用户也可以从集合管理视图中进行此操作。Similarly, users who have permission to delete a team project can do so from the collection administration view.


Release Management:新功能和改进 Release Management: new features and improvements

  • 新版本的基于 Web 的 Release Management。New version of web-based Release Management. Release Management 现已集成到 TFS 中。Release Management is now integrated into TFS. 在通过 Web 访问 TFS 时,可以直接从发布中心访问 Release Management 功能,而无需单独安装服务器或客户端。You can access Release Management features directly from the RELEASE hub in TFS web access without having to install a separate server or client. 与早期版本相比,这一新版 Release Management 更易于使用,且采用 TFS 中的新生成系统的基础结构和体验。This new version of Release Management is simpler to use than the earlier version and is based on the same infrastructure and experience as the new Build system in TFS.
    • 简化了将应用程序部署到本地服务器、SCVMM 或 VMware 托管的虚拟机或 Azure 的流程。Simplify your application deployment to on-premises servers, SCVMM- or VMware-managed virtual machines, or to Azure.
    • 通过设置发布定义(触发器按顺序或并行对环境进行部署)来控制部署。Control your deployments by setting up release definitions that trigger deployments to environments in sequence or in parallel. 跟踪工作项、提交、生成和已部署的发布。Track how far your work items, commits, builds, and releases have been deployed.
    • 可以为未通过的测试创建 bug。You can create bugs for failed tests. bug 中会自动填充错误消息和堆栈跟踪等调试信息。Debug information, like error message and stack trace, will be auto-populated in the bug.

请参阅这一新版本相关的文档和一些最新的博客文章There's documentation about this new version and some recent blog posts.

  • 用于与 VMWare 集成的新扩展。A new extension for integration with VMWare. 从 Visual Studio Team Services 或 TFS 连接到 VMWare vCenter 服务器,并在 vCenter 托管的虚拟机上创建、删除和应用快照。Connect to a VMWare vCenter server from Visual Studio Team Services or from TFS and create, delete, and apply snapshots on virtual machines that are managed in vCenter. 对于 VMWare 托管的虚拟机,以动态方式为虚拟机预配或将其还原为干净的快照,然后创建要部署的生成和发布定义。For virtual machines that are managed in VMWare, dynamically provision or restore them to a clean snapshot, then create build and release definitions to deploy. 请从 Marketplace 获取此新扩展Get this new extension from the Marketplace.
  • 适用于 System Center Virtual Machine Manager (SCVMM) 的新扩展。A new extension for System Center Virtual Machine Manager (SCVMM). 连接到 SCVMM 服务器,并在 SCVMM 管理控制台托管的虚拟机上创建、删除和应用快照。Connect to a SCVMM server and create, delete, and apply snapshots on virtual machines that are managed in SCVMM administration console. 现在可以复制 TFS Lab Management 的一项关键功能:在将 SCVMM 托管的虚拟机还原为干净的快照后,创建要部署到这些虚拟机的生成和发布定义。Now you can replicate one of the key features from TFS Lab Management: create build and release definitions to deploy to virtual machines that are managed in SCVMM after you've restored them to a clean snapshot. 请从 Marketplace 获取此新扩展Get this new extension from the Marketplace.
  • 生成摘要中的部署部分。A deployments section in build summary. 这一新增的部分显示了已通过 Release Management 部署了生成的环境列表。This new section shows a list of environments where a build has been deployed through Release Management. 还可以在此部分中新建发布。You can also create a new release from this section.


  • 在创建和部署发布时设置目标环境。Set target environments when you create and deploy a release. 我们新增了一项功能来替代自动部署。We've added the ability to override automatic deployment. 如果想禁用自动部署到特定环境这一功能,请转到“新建发布”对话框中的“自动部署”部分。安全性的说明:只有发布定义作者才能灵活地编辑各环境的部署流图。When you want to turn off automatic deployment to specific environments, go to the Automated deployments section in the Create New Release dialog box.A note on security: The flexibility to edit the deployment flow graph across environments is still restricted to release definition authors only.


  • 按计划新建发布。Create new releases on a schedule. 我们新增了一项功能,可方便设置创建新发布的时间表。We've added the ability to set up a schedule for creating new releases. 成功的生成项目的最新版本是按计划时间进行选择的。The latest version of successful build artifacts is picked up at the scheduled time. 在创建发布后,系统会根据这些环境上配置的部署条件来确定是否自动部署到环境。Once the release is created, automatic deployment to environments is determined by the deployment conditions configured on those environments. 若要配置用于新建发布的计划触发器,请转到发布定义中的“触发器”选项卡。To configure a scheduled trigger for creating new releases, go to the Triggers tab in the release definition.


发布摘要中显示的测试结果 Test results available in the Release summary

若要查看测试质量并分析测试结果,可以查看“发布摘要”中的“测试”选项卡,了解已运行测试的每个环境的测试状态。To view test quality and analyze test results, the Tests tab in the Release summary will show you test status of each environment in which tests have run. 状态消息包括在特定环境中或在所有环境的整个发布期内已通过和未通过的测试数、通过百分比以及测试持续时间。The status includes count of passed and failed tests, pass percentage, and test duration for a particular environment or for the entire release, across all environments. 无需离开“发布摘要”页,即可通过深入了解错误消息、堆栈跟踪和测试附件来查找未通过的测试。You can drill down into the error message, stack trace, and test attachments to look for failed tests - without leaving the Release summary page.


重新排序板上的卡 Reordering cards on boards

针对团队的工作方式来优化板。Optimize boards for the way your team works. 现在可以指定在更改列时如何重新排序卡:无限制重新排序,还是严格按照积压工作 (backlog) 顺序重新排序。You can now specify how cards will be reordered when you change columns: reorder with no restrictions or strictly follow the backlog order.

删除工作项 Deleting work items

现在可以删除工作项,获得完整的回收站体验!You now have the ability to delete work items, complete with a recycle bin experience! 此功能取代了“已删除”状态。This capability replaces the Removed state. 我们已经将“删除”作为唯一权限进行实现,因此你可以精细控制谁有权访问此功能。We’ve implementeddelete as a unique permission, so you have fine-grained control over who has access to this capability.


全局快捷键 Global shortcut keys

引入代码中心和工作中心的键盘快捷方式!Introducing keyboard shortcuts for the Code and Work hubs! 导航时手都不需要离开键盘。Navigate without ever taking your hands off the keyboard.


仪表板编辑模式 Dashboards edit mode

我们在所有仪表板中都新增了一个模式,即编辑模式。We’ve added a new mode called edit mode to all dashboards. 只有在选择编辑模式后,才能移动小组件,从而减少了“不小心”移动小组件发生的机会。Widgets won't move unless you select edit mode, reducing the chances of "accidentally" moving a widget. 处于编辑模式时,可以删除、重新排列和配置小组件以及添加新的小组件。While you're in edit mode, you can remove, rearrange, and configure widgets, as well as add new widgets.


自动刷新仪表板 Auto-refresh dashboards

我们添加了一个选项,用于每 5 分钟自动刷新一次特定仪表板。We've added an option to auto-refresh a specific dashboard every 5 minutes. 这样一来,可以让仪表板显示在电视监视器或走廊屏幕上并随时更新。This is a great way to put the dashboard on your TV monitor or hallway screen and keep it updated.

每 5 分钟自动刷新一次仪表板的选项

仪表板目录中的生成小组件 Build widgets in the dashboard catalog

从仪表板目录添加生成历史记录图表的新选项便于你直接从仪表板配置生成定义。A new option to add a build history chart from the dashboard catalog lets you configure the build definition directly from the dashboard. 请阅读介绍仪表板未来趋势的博客,以了解我们如何在仪表板中引入其他图表时不断提升可发现性和易用性。Read thedashboards futures blog to learn how we’re improving the discoverability and ease in bringing different charts to your dashboard.

仪表板目录中的工作项查询图表 Work item query charts in the dashboard catalog

现在可以将工作项查询图表从小组件目录添加到仪表板中。You can now add charts for work item queries to the dashboard from the widget catalog. 这些图表是可配置的。These charts are configurable. 可以在不离开仪表板上下文的情况下,选择查询、图表类型和可视化选项。You can choose a query, a chart type, and visualization options while staying in the dashboard context. 图表类型包括饼图、条形图、柱形图​​、堆积条形图、折线图​​、分区图和堆积面积图。Chart types include pie, bar, column, stacked bar, line, area, and stacked area. 还可以在数据透视表中显示数据。You can also display data in a pivot table. 另外,仍可以从工作中心的图表选项卡添加图表,然后按一贯的做法配置这些图表。And, you can still add charts from the Charts tab in the Work hub and configure them just like you've always done.


@mentions 和 #ID @mentions and #ID

现在可以使用 @ 符号 在拉取请求讨论(包括提交、变更集或搁置集讨论)中提及人员。Now you can use the @ symbol to mention people in pull request discussions, including commit changeset and shelveset discussions.

如果在讨论中提及某人,此人将收到电子邮件通知,其中包括该讨论以及指向拉取请求、提交、变更集或搁置集的链接。When you mention a person in a discussion, they receive an email alert that includes the discussion and a link to the pull request, commit, changeset, or shelveset. 人员提及是可单击的,并会显示标识卡以及其他详细信息。People mentions are clickable and display an identity card, with additional details. 如果你提及的人员无权访问拉取请求、提交、变更集或搁置集,那么你将会收到一封电子邮件,通知你 @mention 失败了。If you mention individuals who do not have permission to the pull request, commit, changeset, or shelveset, you’ll receive an email indicating that the @mention has failed.

此外,现在还可以使用 # 符号 在拉取请求讨论(包括提交、变更集或搁置集讨论)中提及工作项。In addition, you can now use the # symbol to mention work items in pull request discussions, including commit changeset and shelveset discussions.

这些工作项是可单击的,并能打开新的选项卡,为你带来熟悉的工作项体验。These work items are clickable and open a new tab, where you’ll see the work item experience that you’re already familiar with.

请注意:我们暂不支持在工作项讨论和代码注释中使用 @/# 提及功能。Note: We don’t currently support @/# mentions in work item discussions and code comments. 我们正在计划在今后的版本的提供此支持。This is something we are planning on supporting in a future release.

拉取请求小组件 Pull request widget

团队管理员现在可以从仪表板目录添加拉取请求小组件。Team admins can now add the pull request widget from the dashboards catalog. 对于特定存储库,用户可通过拉取请求小组件查看已分配给团队、已分配给用户本身以及由用户创建的拉取请求。对于特定存储库,用户可通过拉取请求小组件查看已分配给团队、已分配给我以及由我创建的拉取请求。For a specific repository, the pull request widget lets users see pull requests that are assigned to the team, assigned to me, and created by me. 用户可以快速导航到各个拉取请求,也可以概览存储库中的拉取请求。Users can quickly navigate to an individual pull request or they can view the summary of pull requests in the repository.

使用 Markdown 小组件可以在代码存储库中选择要显示的现有文件 Markdown widget lets you choose an existing file in a code repository to display

现在可以在现有存储库中选择要显示的任意 Markdown 文件。You can now choose to display any markdown file in your existing repository. 还可以直接从代码资源管理器将文件添加到团队项目中的任意仪表板。You can also add the file to any dashboard in your team project directly from the Code Explorer.


常用标识选取器 Common identity picker

我们正在提升在版本控制、发布管理和 @mention 区域中搜索和发现用户和组的体验。We're rolling out an improved experience to search and discover users and groups in version control, release management, and @mention areas. 用户现在可以对显示名称(如“john doe”)和 SAM-Account-Name(如“jdoe”)等属性执行基于前缀的搜索。Users can now do prefix-based searches on attributes like Display Name (such as ‘john doe’) and SAM-Account-Name (such as ‘jdoe’).

对显示名称或 SAM-Account_Name 等属性执行基于前缀的搜索

Team Foundation 版本控制的封闭签入 Gated check-in for Team Foundation Version Control

TFVC 项目现在可以设置分支策略,从而要求先成功完成生成,然后才能将任意代码提交到分支中。TFVC projects can now have branch policies to require a successful build before any code can be submitted into a branch.

版本控制 Web Version control web

代码中心新增了多项功能,并进行了大量的可用性和样式改进。The CODE hub has several new features and numerous usability and style improvements. 代码资源管理器现在可显示选定分支的最新生成状态,并全部采用了全新的现代图标,便于在高分辨率显示屏上查看。The Code Explorer now shows the status of the latest build for the selected branch, and has all new, modern icons to improve readability on high resolution displays.


拉取请求中心改进了视图,以突出显示你创建的拉取请求,以及分配给你和你的团队的拉取请求。The Pull Requests hub has improved views to highlight the pull requests you've created and those assigned to you and your team. 通过全新的链接体验,改进了拉取请求、工作项和提交之间的可跟踪性。Traceability between pull requests, work items, and commits has been improved by new linking experiences.


Team Foundation Server 扩展 Team Foundation Server extensions

扩展通过添加新功能或与现有服务集成,带来了集成体验,从而扩展和提升了 Team Foundation Server Web 体验。Extensions enable integrated experiences that extend and enhance the Team Foundation Server web experience, either by adding new capabilities or integrating with existing services.

可以将本地扩展上传到 Team Foundation Server ,并在特定团队项目集合上安装这些扩展。On-premises extensions can be uploaded to Team Foundation Server and installed on specific team project collections.

也可以从 Visual Studio Marketplace 下载扩展,并将其上传到 Team Foundation Server。Extensions can also be downloaded from the Visual Studio Marketplace and uploaded to a Team Foundation Server.

可以将本地扩展上传到 Team Foundation Server ,并在特定团队项目集合上安装这些扩展。

Keyboard shortcuts for Kanban board

现在可以在看板上单击工作项,然后对常用任务使用键盘快捷键。You can now click a work item on the Kanban board and use keyboard shortcut keys for common tasks. 下面的示例展示了可以执行的操作:Here's a sample of what you can do:

  • 创建新工作项create new work items
  • 在列和泳道内或跨列和泳道移动工作项move work items within or across columns and swimlanes
  • 展开和折叠工作项expand and collapse work items

改进了代码和工作项之间的链接 Improved linking between code and work items

除了提交链接之外,我们还新增了其他链接功能。In addition to commit linking, we've added new linking capabilities. 可以将工作项链接到 GIT 分支和拉取请求,也可以直接从积压工作项或看板创建分支链接。You can link work items to Git branches and pull requests and also create branch links directly from backlog items or the Kanban board.

显示如何在看板上创建分支链接Shows how to create branch links on the Kanban board with

在创建拉取请求时,链接到源分支或提交的任意工作项将自动链接到新的拉取请求。When you create a pull request, any work items linked to the source branch or the commits will automatically be linked to the new pull request. 拉取请求详细信息视图也经过了更新,现包括“相关工作项”部分。The pull request details view has also been updated to include a Related Work Items section. “相关工作项”部分列出了链接到给定拉取请求的所有工作项,并简化了链接更多工作项的流程。The Related Work Items section lists all of the work items that are linked to a given pull request and provides a simple experience for adding links to more work items.

拉取请求详细信息视图也经过了更新,现包括“相关工作项”部分。The pull request details view has also been updated to include a Related Work Items section.

  • 生成管理。Build administration. 生成队列的管理员现在可以控制谁能够创建使用给定队列的生成和发布定义。Administrators for build queues can now control who is able to create build and release definitions that use a given queue. 这样,团队便能在给定帐户或项目集合内拥有自己的生成资源。This allows a team to have its own build resources within a given account or project collection.
  • 历史统计信息。Historical statistics. 生成和发布代理的历史统计信息可以从队列和池视图中获取。Historical statistics for build and release agents are available from the queue and pool view. 这样,生成管理员可以更好地了解给定生成资源的使用情况。This can give build administrators a better understanding of how much usage there is for a given build resource.
  • 生成界面改进。Build interface improvements. 我们简化了用于创建新生成定义的界面。We've simplified the interface for creating new build definition. 可以在选择模板后设置有关用户资源和队列的关键信息。You can set key information about your sources and queue after selecting a template.
  • 扩展生成结果视图。Extend build results view. 通过使用扩展框架,可以在生成结果(有时称为生成摘要)视图中扩展显示自定义信息。The build result (sometimes called build summary) view can be extended with custom information and views by using the extension framework. 还可以通过发布使用此命令的简单的 markdown 文件扩展视图:##vso[task.addattachment type=Distributedtask.Core.Summary;name=myattachmentname;]c:\myattachment.mdYou can also extend the view by publishing a simple markdown file using this command: ##vso[task.addattachment type=Distributedtask.Core.Summary;name=myattachmentname;]c:\
  • 将任务作为扩展发布。Publish tasks as extensions. 可以使用库将生成和发布任务作为扩展的一部分进行发布。Using the gallery, build and release tasks can be published as part of an extension.

测试:新功能和改进 Testing: new features and improvements

Build vNext 中的计划测试Planned testing in Build vNext

如果已对使用测试计划和测试套件的佳话测试投入了资源,则可以使用运行功能测试任务在 Build vNext 中触发自动运行。If you've invested in planned testing using test plans and test suites, you can trigger automated runs in Build vNext by using the Run Functional Tests task. 结果显示在“生成摘要”页上的“测试”选项卡中以及测试中心内。Results are displayed in the Tests tab on the Build Summary page, as well as in the Test Hub. 我们在“测试”选项卡上新增了一个“分组依据”选项。通过按测试套件分组,可以快速查看已运行的所有套件及其质量。We've added a new Group By option on the Tests tab. Grouping by Test Suite gives you a quick view of all suites that were run and their quality.

生成中的测试结果Test results in build

下面介绍的功能和改进有助于在“生成摘要”页中分析测试结果:There’s help for you to analyze test results in the Build summary page:

  • 生成中所有测试运行的测试结果汇总摘要。An aggregate summary of test results across all test runs in the build.
  • bug 中首次未通过的测试被标记为新失败,以帮助标识回归。Tests failing for the first time in the bug are flagged as New failures to help you identify regressions. 对于在多个生成中持续未通过的测试,可以查看失败的停滞情况,并导航到出现失败的生成中。For tests that continue to fail across multiple builds, you can see how stale the failures have become and navigate to the build in which a failure was introduced.
  • 显示未通过的测试数以及最近 10 个生成的测试持续时间的趋势图表。Trend charts that show the count of failed tests and test duration for the last 10 builds. 可以将这些图表添加到仪表板中。You can add these charts to the dashboard.
  • 改进了代码覆盖率报表,以显示生成与生成之间增量的图示视图。Code coverage reporting has been enhanced to show a pictorial view with build-to-build deltas.
  • 现在在生成完成电子邮件通知中会显示测试状态。Test status is now available the build completion email notification.


任务改进:Task improvements:

  • 已将使用测试代理任务的 Visual Studio 测试重命名为“运行功能测试”。Visual Studio Test using Test Agent task has been renamed to Run Functional Test.
  • Visual Studio 测试任务和“运行功能测试”任务更快速、更直观且更易用。The Visual Studio test task and the Run Functional Test tasks are faster, more intuitive, and user-friendly.
  • 我们在“发布测试结果”任务中增加了对 xUnit、NUnit、Junit 和 .trx 文件格式的支持。We’ve added support for xUnit, NUnit, Junit and the .trx file format to the Publish Test Results task.
  • “发布代码覆盖率”这项新任务从 Jacoco 和 Cobertura 代码覆盖率工具上传数据。A new task, Publish Code Coverage, uploads data from Jacoco and Cobertura code coverage tools.
  • 另外,我们还完成了大量工作,以便我们的 Java 用户可以将结果和代码覆盖率信息发布到 TFS 中。In addition, a lot of work has been done to enable our Java users to publish results and code coverage information to TFS. 有关信息请阅读“Java 中的测试”部分。Read about it in the section, "Test in Java."

手动测试改进:Manual testing improvements:

  • 筛选测试计划。Filter test plans. 为测试计划设置基于工作项查询的筛选器。Set a work item query based filter for test plans.
  • 显示子套件中的测试。Show test from child suites. 单击一次即可查看当前套件及其子套件中的所有测试。See all tests that are present in the current suite and their child suites, with one click.
  • 删除测试计划。Delete test plans. 此版本推出了最受关注的 UserVoice 测试项之一。One of the top UserVoice items for test is available in this release. 现在可以直接从测试中心删除计划。Now you can delete plans directly from the Test Hub.

Web 上的探索测试 (XT)Exploratory testing (XT) on the web

了解 Web 上的探索测试,并开始从 Marketplace 安装 Chrome 浏览器插件。Learn about exploratory testing on the web and get started by installing the Chrome browser plug-in from the Marketplace. 功能包括:Features include:

  • 捕获屏幕快照和注释。Capture screenshots and notes. 简化了使用内联批注功能捕获注释和屏幕快照的过程。Simplified capture of notes and screenshots with inline annotation capability.

  • 创建 bug 和任务。Create bugs and tasks. 将在探索测试期间发现的问题作为 bug 或任务进行捕获。Capture the issues found during the exploratory testing as either Bugs or Tasks. 自动为你捕获注释、已批注的屏幕快照、视频、图像操作日志、团队区域和迭代路径,以及系统和浏览器信息。The notes, annotated screenshots, videos, image action logs, team area and iteration paths, and system and browser information are captured for you automatically.

  • 搜索和更新现有 bug。Search and update existing bugs. 在创建 bug 时,扩展会根据标题匹配项自动搜索并列出现有 bug。As you create a bug, the extension will automatically search and list existing bugs based on the Title match. 可以选择使用新信息更新现有 bug,从而可以避免重复的 bug。You have the option to update an existing bug with the new information so you can avoid duplicate bugs.

  • 搜索工作项。Explore work items. 对特定工作项执行探索测试。Do exploratory testing for a specific work item. 这样,便可将选定的工作项与正在进行的测试会话相关联,并从扩展内部查看验收条件和说明。This lets you associate the selected work item with your ongoing testing session and view the acceptance criteria and description from within the extension. 这样做还可以在你存档的 bug 或任务与所选工作项之间实现端到端可跟踪性。It also creates end-to-end traceability between bugs or tasks that you file and the selected work item. 可直接从工作项或从扩展内部探索工作项:You can explore the work item either directly from a work item or from within the extension:

    • 直接从工作项探索。Directly from a work item. 直接从产品内部启动特定工作项的探索测试会话。Launch exploratory testing session for a specific work item directly from within the product. 我们已在所有卡片、网格上和测试中心内添加了入口点。We’ve added entry points on all cards, grids, and in the Test hub.
    • 从扩展内部探索。Within the extension. 从 XT 会话内部搜索工作项,然后将其与正在进行的会话相关联。Search for a work item from within the XT session and then associate it with the ongoing session.
  • 数据集合 - 图像操作日志。Data collection - image action log. 现在只需单击一次,即可选择添加自动生成 bug 的步骤。Now you have the option to add the steps that lead to the bug automatically with just one click. 选择“包含图像操作日志”选项可以捕获鼠标、键盘和触摸操作,并将相应的文本和图像直接添加到 bug 或任务中。Select the Include image action log option to capture the mouse, keyboard, and touch actions and add the corresponding text and images directly into the bug or task.

  • 根据图像操作日志创建测试用例。Create test cases based on image action log. 同步测试设计和测试执行是真正探索测试的基础。Simultaneous test design and test execution is the basis of true exploratory testing. 已自动为你提供在探索测试会话和执行测试步骤期间使用图像创建测试用例的功能。Create test cases during your exploratory testing session and the test steps, with images, are automatically filled in for you. 可以编辑捕获到的文本、添加预期结果、排除不相关的行,以及保存文本以便通过和运行后续测试。You can edit the text that's captured, add the expected result, exclude rows that aren't relevant, and save the text for upcoming test passes and runs.

  • 支持屏幕录制。Support for screen recording. 现在可以使用按需屏幕录制来捕获对所有这些问题的发现,这些内容也将自动附加到存档的任务或 bug 中。You can now capture your findings for all those problematic issues by using on-demand screen recording, which will be automatically attached to the task or bug that you file. 我们未来将提供音频支持。Support for audio is coming next.

  • 连接到设备。Connect to devices. 使用基于浏览器的仿真器或 Perfecto 等设备云提供程序在设备上测试应用程序。Test your application on devices by using browser-based emulators or device cloud providers like Perfecto.

  • 独立模式。Standalone mode. 现在,无需连接到 Visual Studio Team Services 或 TFS,即可记下批注、获取屏幕快照(并根据需要进行批注)以及创建 bug。Now you can jot down notes, take screenshots (and annotate them if you want to), and create bugs without connecting to Visual Studio Team Services or to TFS. 在包含所有创建的 bug、屏幕快照和批注的详细信息的报告中,与团队分享发现。Share your findings with your team in a report that includes details of all the bugs you created, screenshots, and your notes.

显示附加有批注和屏幕快照的新 bug 的 TS 独立模式的图像

Java 中的测试 Test in Java

  • 支持 JUnit。Support for JUnit. 可以通过 Ant、Gradle 和 Maven 任务将 JUnit 结果上传到 TFS。You can upload JUnit results to TFS from Ant, Gradle, and Maven tasks.
  • “发布测试结果”任务支持 JUnit。Support for JUnit in Publish Test Results task. 使用其他命令行工具运行测试,并将结果上载到 TFS 中。Run tests using a different command line tool and upload results to TFS.
  • 代码覆盖率支持。Code Coverage support. 从 Jacoco 和 Cobertura 中选择一个作为 Java 项目的代码覆盖率工具。Choose between Jacoco and Cobertura as Code Coverage tools for your Java project. 随时随地修改生成文件,以使用正确的工具并将结果上传到 TFS 中。The build file is modified on the fly to use the correct tool and the results are uploaded to TFS.
  • “发布代码覆盖率”任务支持 Jacoco 和 Cobertura。Publish Code Coverage task supports Jacoco and Cobertura. 如果生成文件已设置为收集代码覆盖率信息,或者你使用的是支持以 Jacoco 或 Cobertura 格式输出结果的其他代码覆盖率工具(如 Istanbul),则可以使用“发布代码覆盖率”任务将代码覆盖率数据上传到 TFS 中。If your build file is already set to collect code coverage information, or if you're using a different Code Coverage tool (such as Istanbul) that supports outputting results in Jacoco or Cobertura format, you can use the Publish Code Coverage task to upload code coverage data to TFS.

其他更改:Bug 修复和已知问题Other Changes: Bug Fixes & Known Issues

有关该版本中的技术改进、Bug 修复和已知问题的完整说明,请参阅以下 MSDN 文章。For a complete description of technology improvements, bug fixes, and known issues in this release, see the following MSDN article.

了解详细信息Team Foundation Server 2015 Update 2 的说明Learn More: Description of Team Foundation Server 2015 Update 2

页面顶端Top of Page