We plan on closing down the corresponding Azure DevOps cloud-based load testing service on March 31st, 2020.
Keeping the pipeline healthy and making it effective is KEY to your DevOps ongoing journey. Some time back we introduced Analytics in Azure Pipeline with Top failing tests report to help you do just that.
I’m excited to share the new navigation we’re working on for Visual Studio Team Services (VSTS) to modernize the user experience and give you more flexibility. As Lori mentioned in her blog post, our goal to create an integrated suite that also gives the flexibly to pick and choose the services that work best for you.
We often get asked how to do CI/CD for IoT apps using Win10 IoT Core. If you’ve been considering or using Win10 IoT Core, then read on.
The Visual Studio Test Platform that ships with Visual Studio 15.6 RTW now supports Testing on Win10 IoT Core.
As you are already aware, we announced the plan for deprecating XAML builds sometime back.
TFS 2018 RC1 is now available and with that XAML builds are no longer supported. Consequently, Lab Management and automated testing capabilities in Microsoft Test Manager (MTM) are no longer supported starting from TFS 2018 RC1.
Having executed a test – at a minimum – we want to know the outcome. But beyond that, we may want to know more. Data collectors and loggers are the key extension mechanisms intended to provide this and other such details for rich reporting.
Updating off pre-RTM bits once RTM ships ought to be routine. But if you have not already done so in the case of the .NET Core based Test projects, let me give you a reason to do so.
vstest delegates discovery and execution of tests to test-framework-specific adapters.
Essential to TIA’s test selection is the map of dynamic dependencies between test methods and source files of code exercised during their execution. TIA needs dependencies mapped in this form:
<span style="font-size: 10pt"> TestMethod1
TIA can generate such a dependencies-map for managed code execution.