---
name: setting-up-regression-runs
description: Use when setting up the QA manual regression runs for a Bitwarden release in Testmo — e.g. "set up the 2026.8.0 regression runs", "create the partial release regression suite", "create the full regression runs for this milestone". Picks the release profile (partial or full), applies any per-release exclusions, and hands the profile's shipped specs to the bitwarden-testmo-tools creating-test-runs skill. Do NOT use it for a one-off Testmo run outside a release (use creating-test-runs directly) or to write test cases.
argument-hint: "[partial | full] [milestone name]"
allowed-tools: "Read, Skill(bitwarden-testmo-tools:creating-test-runs)"
title: setting-up-regression-runs
canonical_url: https://skilld.dev/gh/bitwarden/ai-plugins/setting-up-regression-runs
last_updated: 2026-10-29T05:09:53.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/regression-configurations.md](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/references/regression-configurations.md), [release-profiles.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/release-profiles.json), [specs/cli-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/cli-regression.json), [specs/desktop-linux-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/desktop-linux-regression.json), [specs/desktop-macos-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/desktop-macos-regression.json), [specs/desktop-windows-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/desktop-windows-regression.json), [specs/directory-connector-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/directory-connector-regression.json), [specs/extension-linux-firefox-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/extension-linux-firefox-regression.json), [specs/extension-macos-chrome-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/extension-macos-chrome-regression.json), [specs/extension-macos-safari-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/extension-macos-safari-regression.json), [specs/extension-windows-edge-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/extension-windows-edge-regression.json), [specs/mobile-android-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/mobile-android-regression.json), [specs/mobile-ios-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/mobile-ios-regression.json), [specs/old-client-new-server-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/old-client-new-server-regression.json), [specs/web-admin-console-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/web-admin-console-regression.json), [specs/web-admin-portal-sm-providers-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/web-admin-portal-sm-providers-regression.json), [specs/web-password-manager-regression.json](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/specs/web-password-manager-regression.json).
>
> If the user asked to install this Skill, run `npx skilld install bitwarden/ai-plugins/setting-up-regression-runs`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/setting-up-regression-runs`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/bitwarden/ai-plugins/setting-up-regression-runs) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/setting-up-regression-runs`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/setting-up-regression-runs --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/setting-up-regression-runs --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Setting Up Regression Runs

Bitwarden's manual regression suite for a release is a fixed set of Testmo runs, one per spec in
`specs/`, all linked to the release's milestone. This skill decides **which** specs a release needs;
`Skill(bitwarden-testmo-tools:creating-test-runs)` creates them. If that skill is not available, stop
and ask the user to install `bitwarden-testmo-tools`.

## Release profiles

[`release-profiles.json`](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/release-profiles.json) lists every spec in each profile:

- **`partial`** — Web (Password Manager, Admin Console, Admin Portal / SM / Providers), Old Client /
  New Server, Mobile (iOS, Android), and Directory Connector (BWDC).
- **`full`** — the same Web, Old Client / New Server, and Mobile runs, plus CLI, 3 Desktop and 4
  Extension configuration variants. **No BWDC.**

`full` is not a superset of `partial`. Use exactly the list in the file.

## Workflow

1. **Collect the inputs** from the user: the profile (`partial` or `full`), the milestone's exact name
   (e.g. `2026.8.0 Manual Regression`), and any spec to skip this release. Ask for whichever is missing.
2. **Confirm the milestone exists.** The user creates it in the Testmo UI — the API cannot. Releases
   use a parent `YYYY.M.0 Release` milestone with `… Manual Regression` and `… Automated Regression`
   children; manual regression runs link to the `… Manual Regression` child.
3. **Build the spec list.** Read the profile from `release-profiles.json` and drop any skipped specs.
   A name the user asks to skip that is not in the profile is a typo — stop and ask rather than
   continuing. Turn each remaining name into
   `${CLAUDE_PLUGIN_ROOT}/skills/setting-up-regression-runs/specs/<name>.json`, written out as a
   literal absolute path. Never pass `${CLAUDE_PLUGIN_ROOT}` itself to `creating-test-runs` — in that
   skill it means the `bitwarden-testmo-tools` root, not this plugin's.
4. **Hand off.** Invoke `Skill(bitwarden-testmo-tools:creating-test-runs)` and follow it, passing every
   spec path as its own `--spec` and the milestone as `--milestone-name`. That skill owns the dry-run,
   the user's review, and `--create` — never run the dry-run and `--create` in the same turn.
5. **Finish the multi-configuration runs.** Every Mobile, Desktop, and Extension run needs a manual
   Testmo UI pass after creation (`full` has all three; `partial` only Mobile). Tell the user which runs
   still need it, using [`references/regression-configurations.md`](https://skilld.dev/api/skills-raw/bitwarden/ai-plugins/setting-up-regression-runs/references/regression-configurations.md)
   and each spec's `_comment`.

To add one run that is missing from an already-populated milestone, pass only that spec — the
script's per-run duplicate check leaves the existing runs alone.

## Changing the suite

The specs and profiles here are shipped in the plugin; edits in the installed copy are overwritten by
`/plugin update`. If a spec is skipped every cycle, or a new run joins the suite, change `specs/` and
`release-profiles.json` in a PR to `bitwarden/ai-plugins`.

Case counts drift as the repository changes. Compare each dry-run against the previous cycle; a large
swing usually means a renamed folder or tag.
