---
title: "Artillery | Skills We Assign For | Azendo"
description: "Artillery for load testing — YAML scenarios, WebSocket support, and the Azendo roles assigned for it."
url: "https://azendo.co/skills/artillery/"
---

[Skills](https://azendo.co/skills/) QA and delivery tooling 

# Artillery.

Artillery is a load testing tool configured in YAML with JavaScript extension points, covering HTTP, WebSocket and Socket.io. It is built to run in CI and to scale out through cloud workers without managing load generators.

## Where Artillery fits on a long engagement.

The YAML-first approach lowers the barrier for simple cases: a basic load test is a short readable file rather than a program. JavaScript hooks cover the cases where declarative configuration runs out, which keeps the common path simple without capping what is possible.

WebSocket and Socket.io support is the differentiator. Real-time features — live updates, chat, collaborative editing — are exactly where load behaviour is hardest to predict and where most HTTP-focused tools cannot help at all.

## What an assigned team does with Artillery.

Real-time systems fail differently under load. Connection counts, message fan-out and memory per connection are the constraints, and they are not visible in a test that only measures request latency.

Designing a test that measures the right thing is the skill, and it sits with the assigned testing capacity under [qa outsourcing](https://azendo.co/services/qa-engineering-and-test-automation/).

## What we use Artillery for.

* Load testing real-time features WebSocket connection counts and fan-out measured, which HTTP tools cannot reach.
* Simple scenarios stated simply A readable YAML file for the common case, with JavaScript available where it is not.
* Running in the pipeline Tests executed on a schedule with thresholds, rather than as a manual exercise.

## How Artillery capacity is assigned.

Artillery is chosen where real-time protocols are part of what needs measuring. The capacity to run it is agreed as a [committed monthly capacity](https://azendo.co/pricing/) across the testing discipline.

## Roles we assign Artillery for

* [Performance Test Engineer QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/performance-test-engineer/)

## Service lines it sits in

* [QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/)

Capacity is agreed as a committed monthly capacity across a discipline, not per skill.

## Related in qa and delivery tooling

* [Jira — skill we assign for](https://azendo.co/skills/jira/)
* [TestRail — skill we assign for](https://azendo.co/skills/testrail/)
* [Jest — skill we assign for](https://azendo.co/skills/jest/)
* [React Testing Library — skill we assign for](https://azendo.co/skills/react-testing-library/)
* [XCTest — skill we assign for](https://azendo.co/skills/xctest/)
* [Espresso — skill we assign for](https://azendo.co/skills/espresso/)
* [Detox — skill we assign for](https://azendo.co/skills/detox/)
* [Flutter Test — skill we assign for](https://azendo.co/skills/flutter-test/)

## Tell us what your roadmap needs Artillery for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)