Azure DevOps Blog

DevOps, Git, and Agile updates from the team building Azure DevOps

Cloud-load testing service is hyper-scale ready: lessons from generating 1M concurrent user load

Every now and then we hear of a business-critical app failing during major promotional or seasonal events such as holiday sales. More often than not it turns out that the app is not ready for the massive demand created on such occasions - causing the servers to fail and resulting in dissatisfied customers and lost opportunity. To ensure that ...

Run cloud-based load tests using your own machines (a.k.a. Bring your own subscription)

When you run a cloud-based load test, the load testing service automatically provisions the necessary machines (load agents) for generating the load to your application. Once the load test run has completed, these resources are torn down. This works well for the most part for a large set of customers. However, some customers want to be able to...

Announcing MSTest V2 Framework support for .NET Core 1.0 RTM

MSTest V2 is now supported on .NET Core 1.0 RTM. API changes in .NET Core 1.0 leading up to RTM (see #7754), were blocking users of the MSTest V2 packages we had released for .NET Core 1.0 RC2. Not any more (see #10713), we are pleased to note. This continues to be a preview release, and comes with following changes...

Testing private/intranet applications using Cloud-based load testing

Cloud-based Load Testing Service can be used for performance and scale testing of an application by generating load from Azure. This type of load generation can only hit/generate load on an internet/publically accessible application. But we have seen many times customer needs to load test their application which is not publically accessible. ...

Use cloud load agents on your infrastructure

This blog talks about how you can configure your own machines (physical/VMs) with Cloud-based Load Testing service to do a load test run. This is primarily useful when you want to load test an application which is not publically accessible. To get more context around this, please refer 'Load testing Applications behind Firewall using Cloud-...

Evolving the Visual Studio Test Platform – Part 2

As promised in the previous post, what follows is a recap of all of the Testing-related features implemented and delivered in the Visual Studio 2015 cycle until now. Each of the features might be relevant at a different stage in the lifecycle, but together they serve the single purpose of enabling efficiency - and overlaid on the lifecycle ...

Evolving the Visual Studio Test Platform – Part 1

Three releases (VS 2015 Update 3, Visual Studio "15" Preview 3, MSTest V2) featuring Test Platform components in as many months indicate a path best traced by starting from the present. The Test Platform Presently, Visual Studio has an open and extensible test platform with tests being written using various test frameworks and run using a ...

The IntelliTest Reference Manual

There is something to be said about having a good tool box - after all picking the right tool for a job is also as much about picking the right job for a tool, and the bigger your toolbox, the better the chances are that the best tool you can muster will be the one appropriate for the job at hand. To get the most productivity improvements ...

Remote testing – Distributing tests based on number of machines

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. You will see a new check box in the task as ...