TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Visual Studio Extension Manifest Configuration

10 posts · Mar 2012 – May 2017

What this trail covers

This thread tracks the evolution of browser-based exploratory testing extensions for Visual Studio Team Services. It provides specific steps for configuring the extension to work with Internet Explorer 11 and Windows 8.1, addressing issues related to Enhanced Protected Mode and add-on enablement. It also includes registry key deletion as a fallback solution and notes that a permanent fix is in progress. This post introduces the ability to perform exploratory testing using Microsoft Test Manager and automatically link test cases and bugs to requirements, building test plans dynamically.

All Microsoft trails
  1. Turn your infrastructure into code with Chef, and update your Assembly information with May's Team Services Extensions RoundupThis post introduces two new extensions for Visual Studio Team Services: Chef and Assembly Info. The Chef extension adds six build and release tasks for configuring Chef Automate, including updating cookbook versions, uploading cookbooks, adding variables to Chef environments, releasing cookbook versions, executing InSpec, and executing Chef Client. The Assembly Info extension adds a build task to configure assembly properties such as Title, Product, Description, Company, Copyright, Trademark, Culture, Configuration, Version Number, and File Version Number.
  2. Test & Feedback extension - Create artifactsThis post details the 'Create' capability of the Test & Feedback extension, focusing on generating actionable work items. It explains how the extension supports creating bugs, tasks, test cases, and feedback responses, automatically populating them with captured data (screenshots, screen recordings, page load times). It also highlights the 'view similar bugs' feature to avoid duplicates and the end-to-end traceability provided by linking created work items to existing ones. The post differentiates between standalone and connected modes of the extension and outlines the work item creation permissions for different user access levels (Basic, Stakeholder).
  3. Test & Feedback - Capture your findingsThis post details the 'Capture' functionality of the Test & Feedback extension for Visual Studio Team Services. It explains explicit capture methods (screenshots with annotation, notes, screen recording) and implicit capture methods (image action log of clicks/typing, page load data, system information). It also covers the extension's options for configuring capture sources.
  4. Install Visual Studio Marketplace extensions directly to Team Foundation ServerThis post introduces the ability to install Visual Studio Marketplace Extensions directly to Team Foundation Server "15" RC1. It details a streamlined process for installing both free and paid extensions by browsing the Marketplace from TFS, which then recognizes the TFS environment and allows selection of a team project collection. The process automatically handles downloading, uploading, and installing the extension into TFS. For paid extensions, it also covers the purchase flow, including subscription selection and user assignment.
  5. The Team Services extension for Visual Studio Code now supports Team Foundation Server 2015 Update 2 and laterThe Team Services extension for Visual Studio Code now supports Team Foundation Server 2015 Update 2 and later. This enables users to manage pull requests, monitor builds, and view work items for TFS Git repositories directly from VS Code. The extension implements secure storage of credentials (username/password for TFS, PAT for VSTS) on Windows, macOS, and Linux.
  7. Team Foundation Server ExtensionsThis post details the process of installing extensions on Team Foundation Server (TFS) 2015 Update 2. It explains how to download .vsix packages from the Visual Studio Marketplace and upload them to TFS, as well as how to build and upload in-house extensions. It also covers installing extensions to a Team Project Collection and provides guidance on next steps and feedback channels.
  8. Announcing the release of the Visual Studio Team Services extension for Visual Studio CodeAnnounces the release of the Visual Studio Team Services extension for Visual Studio Code. This extension allows users to manage pull requests for Team Services Git repositories, monitor builds, and view work items directly within VS Code. It provides status bar indicators for active pull requests and build status, and enables navigation to the web interface for detailed actions. The extension also supports commands for viewing work items assigned to the user, creating bugs/tasks, viewing build summaries, and accessing blame/history information. The extension is open-sourced on GitHub.
  9. Announcing easy to use browser-based exploratory testing for Visual Studio Team ServicesThis post introduces a new browser extension for Visual Studio Team Services (VSTS) that facilitates exploratory testing. The extension allows users to document tests, capture and annotate screenshots, file bugs, and test smart devices. It integrates with Perfecto Mobile for device testing. The post outlines a four-step process for getting started: downloading the extension from the Visual Studio Marketplace, installing it, connecting it to a VSTS account, and then performing exploratory testing. Specific features highlighted include image annotation tools, cross-browser tab and instance support, and device testing via Perfecto Mobile integration.
  10. Multiple Monitor Support for Windows Store Apps in Visual Studio 2013 Update 3Added persistence to remember which screen a Store app was occupying when debugging stopped. This feature is active when the app is closed using 'Stop Debugging', 'Suspend', or 'Suspend and Shutdown'.
  11. Using Internet Explorer 11 and not able to record a web performance test successfully?This post provides a workaround for enabling the Microsoft Web Test Recorder add-on in Internet Explorer 11 and Windows 8.1 for Visual Studio Web Performance tests. It details disabling 'Enhanced Protected Mode' in Internet Explorer's advanced settings and ensuring the 'Microsoft Web Test recorder 10.0' add-on is enabled. A fallback solution involving deleting specific registry keys is also provided.
  12. Changing fields on the Visual Studio Extension Gallery pageThis post details how to modify the VSIX manifest file to change fields on the Visual Studio Extension Gallery page, specifically addressing 'Supported Versions' and 'Supported Visual Studio 2010 Editions'. It explains how to edit the manifest as an XML file to add support for multiple Visual Studio versions (e.g., 10.0 and 11.0) and their editions, and notes that the VSIX format has changed in VS 2012 but older formats are still supported.
  13. Automatic requirement traceability with Exploratory TestingThis post details how Microsoft Test Manager automatically builds test plans during exploratory testing sessions. When a user explores a backlog item, the system automatically creates test cases and bugs, which are then added to a requirement-based suite within the test plan. This eliminates manual test case creation and organization, saving effort and ensuring that test plans are dynamically updated with the results of exploratory testing.
  14. Changing the default filter for exploratory testingThis post details how to change the default query filter for exploratory testing in Microsoft Test Manager. Users can edit the query to include different work item categories (e.g., bugs) and specify area paths. The post provides screenshots and step-by-step instructions for modifying the query and saving the changes, as well as an option to reset to the default query.
  15. Getting Started with Exploratory TestingThis post introduces the capability to perform exploratory testing using Microsoft Test Manager 11. It details the process of exploring applications, filing bugs with rich actionable information (screenshots, comments, attachments), and simultaneously building regression test suites. Key features highlighted include associating testing with product backlog items for traceability, capturing screenshots with comments, attaching log files, creating bug work items with pre-populated details, and creating test cases from exploratory sessions. The post also describes the summary of exploratory test sessions and the automatic linking of created work items to parent backlog items, effectively building a regression test suite.
  16. Visual Studio 11 Beta: Manual Testing of Windows Metro Style AppsThis post details new manual testing features for Windows Metro style apps in Visual Studio 11 Beta, focusing on testing on remote devices. It introduces the availability of data diagnostic adapters (Event Log, System Info, Action Log) for Windows 8 Devices, the ability to install Windows metro style apps from Microsoft Test Manager on remote devices, and the enhanced Image Action Log for bug creation. The Image Action Log includes text descriptions, control thumbnails, and full screenshots, with specific logic for capturing 'After Images' or 'Before Images' based on navigation. It also elaborates on Action Log quality metrics (Completeness & Readability) and how they are achieved through low-level hooks, touch input redirection, UI Automation, and smart vicinity algorithms for control naming. Exploratory testing on remote devices is also highlighted, along with setup instructions for using a single machine with Visual Studio Remote Tools.