Team Foundation Server 2015 Update 2 版本資訊Team Foundation Server 2015 Update 2 Release Notes

|開發人員社群 |系統需求和相容性 |授權條款 |TFS DevOps Blog |Sha-1 雜湊 | |最新的 Visual Studio 2019 版本資訊|| Developer Community | System Requirements and Compatibility | License Terms | TFS DevOps Blog | SHA-1 Hashes | | Latest Visual Studio 2019 Releases Notes|


這不是最新版的 Team Foundation Server。This is not the latest version of Team Foundation Server. 若要下載最新版本,請瀏覽 Team Foundation Server 2018 Update 3 的最新版本資訊To download the latest release, please visit the current release notes for Team Foundation Server 2018 Update 3. 若要變更此頁面的語言,請按一下頁尾的地球圖示,然後選取您想要的語言。You can change the language of this page by clicking the globe icon in the page footer and selecting your desired language.

本文提供 Team Foundation Server 2015 Update 2 的相關資訊。In this article, you will find information regarding Team Foundation Server 2015 Update 2.


Team Foundation Server 2015 Update 2.1 修正自 Update 2.0 以來的一些 Bug。Team Foundation Server 2015 Update 2.1 has had some bug fixes since Update 2.0. 如需修正的清單,請參閱 KB3160281Please 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.

若要深入了解 Team Foundation Server 2015,請參閱 Team Foundation Server 的需求與相容性 (英文) 頁面。To learn more about Team Foundation Server 2015, see the Team Foundation Server Requirements and Compatibility page.

如需詳細資訊,請參閱 TFS 安裝頁面。Please see the TFS Install page for more information.


Release Notes Icon _ 發行日期:2016年5月5日*_ Release Date: May 5, 2016*

Team Foundation Server 2015 Update 2 的新功能摘要Summary of What's New in Team Foundation Server 2015 Update 2

功能更新:Feature updates:

Team Foundation Server 2015 Update 2 的新功能詳細資料Details of What's New in Team Foundation Server 2015 Update 2

改進 Team 專案建立及刪除體驗 Team project creation and deletion experience improvements

您可以選擇從 Web 體驗和透過 REST API 來建立與刪除 Team 專案。We are 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. 有權建立 Team 專案的使用者,可以從集合管理檢視或瀏覽下拉式清單來完成。Users who have permission to create team projects can do so from the collection administration view or the navigation drop-down list. 如需詳細資料,請參閱建立 Team 專案 (英文)。See creating a team project for more details.

現在可以從網頁體驗和透過 REST API 來建立與刪除 Team 專案。

同樣地,有權刪除 Team 專案的使用者,可以從集合管理檢視來完成。Similarly, users who have permission to delete a team project can do so from the collection administration view.

您可以從集合管理檢視來刪除 Team 專案

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. 您可以直接從 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 are 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 is documentation about this new version.

  • 可與 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 have 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 was 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 have 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 have 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 you create the release, 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. 您現在可以指定在變更資料行時,如何將卡片重新排序:重新排序時沒有限制,或是嚴格遵循待辦項目順序。You can now specify how cards are 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 have implemented delete 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 have added a new mode called edit mode to all dashboards. 小工具會等到您選取編輯模式才會移動,可減少「意外」移動小工具的機會。Widgets will not 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 have 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.

儀表板目錄中的工作項目查詢圖表 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. 此外,您仍然可以從工作中樞的 [圖表] 索引標籤新增圖表並加以設定,就如往常一樣。Additionally, you can still add charts from the Charts tab in the Work hub and configure them just like you have 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.

注意:目前尚未在工作項目討論與程式碼註解中支援 @/# mention。Note: We do not 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 系統管理員現在可以從儀表板目錄新增提取要求小工具。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. 您也可以直接從 Code Explorer 將檔案加入 Team 專案的任何儀表板中。You can also add the file to any dashboard in your team project directly from the Code Explorer.

直接從 Code Explorer 將檔案加入儀表板中

通用身分識別選擇器 Common identity picker

在版本控制、發行管理和 @mention 區域,我們即將推出搜尋和探索使用者與群組的改善體驗。We are 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 have branch policies to require a successful build before any code is submitted into a branch.

版本控制網頁 Version control web

程式碼中樞有數項新功能及許多可用性和樣式改善。The CODE hub has several new features and numerous usability and style improvements. Code Explorer 現在會顯示所選分支的最新組建狀態,並且具有所有新增的新式圖示,以便在高解析度顯示器上更易於閱讀。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 have created and those assigned to you and your team. 新的連結體驗改善了提取要求、工作項目和認可之間的可追蹤性。Traceability between pull requests, work items, and commits were improved by new linking experiences.


Team Foundation Server 擴充功能 Team Foundation Server extensions

擴充功能藉由新增新功能或與現有服務整合,以啟用整合式體驗,進而擴充並加強 Team Foundation Server 網頁體驗。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 並安裝在特定的 Team 專案集合上。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 並安裝在特定的 Team 專案集合上。

工作流程看板的鍵盤快速鍵 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 have 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 are automatically 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 have 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 have 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 have 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 is 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 was enhanced to show a pictorial view with build-to-build deltas.
  • 現在可於完成組建電子郵件通知中看到測試狀態。Test status is now available the build completion email notification.


工作改進項目:Task improvements:
  • 使用 Test Agent 工作的 Visual Studio Test 已重新命名為「執行功能測試」。Visual Studio Test using Test Agent task was 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 have 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, we completed a lot of work to give our Java users the ability 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. 這一版提供測試的其中一個最重要的使用者意見專案。One of the top user feedback items for test is available in this release. 現在您可以直接從測試中樞刪除計劃。Now you can delete plans directly from the Test Hub.
網路上的探勘測試 (XT)Exploratory testing (XT) on the 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 automatically captured.

  • 搜尋及更新現有的錯誤 (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 have 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 captured text, 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 automatically attaches 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. 現在您可以記下附註、取得螢幕擷取畫面 (您想要的話也可以加以標註),以及建立錯誤 (bug),而不必連線到 Visual Studio Team Services 或 TFS。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.

TS 獨立模式的影像,其中顯示附加了附註和螢幕擷取畫面的新錯誤 (bug)

以 JAVA 測試 Test in Java

  • 支援 JUnit。Support for JUnit. 您可以將 JUnit 結果從 Ant、Gradle 和 Maven 工作上傳到 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. 如果組建檔案已設為收集程式碼涵蓋範圍資訊,或是您使用不同的程式碼涵蓋範圍工具 (例如 Istanbul) ,且該工具支援以 Jacoco 或 Cobertura 格式輸出結果,則可以使用「發行程式碼涵蓋範圍」工作,將程式碼涵蓋範圍資料上傳到 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 修正和已知問題Bug Fixes & Known Issues

如需此版本的技術改善、Bug 修正及已知問題的完整描述,請參閱下列 MSDN 文章:Team Foundation Server 2015 Update 2 說明For a complete description of technology improvements, bug fixes, and known issues in this release, see the following MSDN article, Description of Team Foundation Server 2015 Update 2.

意見反應與建議Feedback & Suggestions

我們很希望聽聽您的意見!We would love to hear from you! 您可以透過開發人員社群回報並追蹤問題,並在 Stack Overflow 上取得建議。You can report a problem and track it through Developer Community and get advice on Stack Overflow. 一如往常,如果有需要優先處理的事項,請前往開發人員社群來新增想法或對現有想法進行投票。As always, if you have ideas on things you would like to see us prioritize, head over to Developer Community to add your idea or vote for an existing one.

Top of Page