Atin Bansal

The Azure Pipelines app for Slack provides rich previews of builds and releases when a URL is pasted to the pipeline ( Link unfurling)

Many of our customers use Slack channels to manage Azure Pipelines. Today, we're making it even easier for you, with a tighter integration that lets you be more productive - even when you're on the go!

I am excited to announce the availability of the Azure Pipelines app for Slack. If you use Slack, you can use the Azure Pipelines app for Slack to easily monitor the events for your pipelines. Set up and manage subscriptions for completed builds, releases, pending approvals and more from the app and get notifications for these events in your Slack channels.

You can now migrate code from an existing TFVC repository to a new Git repository within the same account. To start migration, select Import Repository from the repository selector drop-down.

Individual folders or branches can be imported to the Git repository,

With the deployment of Sprint 103, we are enabling users to track the quality of their Requirements right on the Dashboard. We already have a solution for Requirements quality for our Planned testing users and we are bringing it to our users who follow Continuous Testing.

A new Code Coverage tab has been enabled on the Build summary page. Users uploading Code Coverage data in Jacoco or Cobertura formats to Visual Studio Team Services will be able to browse the html report generated by the tool in the Code Coverage tab.

With Sprint 102 deployment on Visual Studio Team Services, we have enabled tests from within an assembly to be distributed to remote machines using the Run Functional Tests task (formerly called Run Tests using Test Agent). This has been one of the bigger asks from customers around Remote testing.

With Sprint 97 deployment on VSTS, users who have invested in planned testing using Test Plan, Test Suites can trigger automated runs in Build vNext. This functionality has been added to the Run Functional Tests task (formerly called Run Tests using Test Agent) as shown below.

Tests broadly classified as integration tests or functional tests are often in need to connect to external app resource (web application, API front end, or a DB tier) to drive validations. Maintaining lifecycle of such tests from the environment where it’s authored (dev machine with VS) to all the other places where they might be consumed (as part of Build/CI Tests,

Users of TFS can do a few simple things to speed up Unit Test execution and improve the overall Build time.
Maximize hardware resource utilization
In most likelihood, you run your tests run on a hardware with multiple cores. To make best use of all the cores,