---
title: "Zephyr | Skills We Assign For | Azendo"
description: "Zephyr for test management — cycles, reporting and automation integration, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/zephyr/"
---

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

# Zephyr.

Zephyr is a test management suite integrating with Jira, covering test case authoring, cycles, execution tracking and reporting, with automation results reported back through its API.

## Where Zephyr fits on a long engagement.

Zephyr's organising idea is the test cycle: a defined set of tests executed against a defined build, which maps onto how regression testing actually happens around a release. Progress and results are tracked per cycle rather than as a flat list of cases.

The recurring problem with any test management tool is maintenance of the case library. Cases accumulate, features change, and a library that has not been pruned contains a significant proportion of tests that describe behaviour the product no longer has. Executing those wastes time and produces failures that mean nothing.

## What an assigned team does with Zephyr.

Library maintenance is invisible work that no release ever prioritises, and it is what decides whether the tool is an asset or an archive.

Treating it as recurring scope rather than something done when it becomes unbearable is part of how standing capacity is agreed under [qa outsourcing](https://azendo.co/services/qa-engineering-and-test-automation/).

## What we use Zephyr for.

* Regression cycles tracked per build A defined set executed against a specific build, with progress visible during the cycle.
* One view of manual and automated results Pipeline results reported in, so release readiness is a single picture.
* A case library that stays current Regular pruning, so executed tests describe the product as it is.

## How Zephyr capacity is assigned.

Library maintenance is counted as scope rather than absorbed silently, which is the kind of recurring work a [committed monthly capacity](https://azendo.co/pricing/) is meant to hold.

## Roles we assign Zephyr for

* [QA Engineer QA and test automation](https://azendo.co/services/qa-engineering-and-test-automation/qa-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 Zephyr 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/)