Azure DevOps and Load Testing

Posted by Load Impact on Oct 11, 2018

If you’re a Microsoft developer or DevOps pro, you’ve heard of Azure DevOps by now. Here, we’ll talk about what Azure DevOps is and how your essential load testing fits in.

Azure DevOps, announced only a few weeks ago, is both an extension and a rebranding of Visual Studio Team Services (VSTS). In short, Azure DevOps includes five major feature “buckets:”

  1. Azure Pipelines. This is the main Azure DevOps CI/CD (continuous integration / continuous delivery) area, and we’ll come back to this to talk about how load testing fits in.
  2. Azure Boards. Here’re your kanban boards, project tracking, agile features, reporting, and so on
  3. Azure Artifacts. This archaeology-sounding category includes package creation, sharing and updates. Package sources can be public or private via Maven, npm, and NuGet.
  4. Azure Repos. View this as a repo management package, file management, collaborative pull requests, and sourcing from any Git repository.
  5. Azure Test Plans. Designed for manual, exploratory testing, this feature lets you explore for feature and performance issues in detail, and somewhat by hand.

Finally, our favorite “feature” of Azure DevOps is its open nature: it’s billed to run with any language on any platform.


Where does load testing fit in with Azure DevOps? Well, it fits in with the first category of features, Azure Pipelines. Azure Pipelines are the automated CI/CD sequences.

These Azure Pipelines can call any test or procedure, just as you’d expect. This feature builds on the old Team Foundation Services (TFS) capabilities. You can easily integrate Load Impact 4.0 and k6 load testing into your Azure Pipelines. (See also this KB article for a step-by-step process for integrating k6 and Load Impact with Azure Pipelines).

We like the new Azure Pipelines automation and workflow features, making it easier for you to build pass/fail logic beyond just “stop if it fails.” Integration (like that with Slack) lets you deliver detailed updates when a test fails. And, of course, since we recommend at least baseline load testing with every build, you’ll catch performance issues quickly.

Your load testing with Azure Pipelines can also take advantage of container support and the ability to deploy to any cloud service - not just Azure.

But ultimately, here’s why we like Azure DevOps: it’s developer-centric. This matches our k6 philosophy to have a developer-friendly performance testing tool that can be used early in the software development lifecycle. The strong Visual Studio heritage of Azure DevOps empowers developers, especially around load testing as part of CI/CD.

Check out Azure DevOps and let us know how your Load Impact load testing integration turns out.

Happy testing!

Topics: azure devops, azure devops load testing, azure devops performance testing

Recent Posts

Popular posts

Posts by Topic

see all

Subscribe to Email Updates