Index of every page on this site: llms.txt
All skills
bitwarden avatar

/setting-up-regression-runs

@a11c77b official
by bitwardenbitwarden/ai-plugins165 stars
27
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/bitwarden/ai-plugins/setting-up-regression-runs

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesregression-configurations.md

≈525 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Regression run configurations (Mobile, Desktop, Extension)

These platforms ship several same-named runs distinguished only by Testmo Configuration. The API can only create step 1 of each; the step 2 UI pass is explained in the bitwarden-testmo-tools creating-test-runs skill's references/multi-configuration-runs.md, and each spec's _comment gives its exact pass.

  • Mobile — 2 runs, both named Mobile. Same filters, differing only by which automation type is excluded. config_id 1 = Android, 3 = iOS.

Desktop and Extension use a broad + narrow split: one variant covers the full folder and the rest are driven by an "essential" tag.

  • Desktop — 3 runs, all named Desktop. Broad = macOS (21); narrow = Windows (22), Linux (20), driven by the desktop-essential tag (id 15999).
  • Extension — 4 runs, all named Extension. Broad = MacOS, Chrome (7); narrow = Windows, Edge (15), MacOS, Safari (10), Linux, Firefox (5), driven by the extension-essential tag (id 17190).

Config and tag ids above verified 2026-08-28 via GET /projects/1/configs and GET /projects/1/tags.

Every variant on both platforms, broad and narrow alike, takes a step 2. The two variant types differ only in how cases are selected:

Broad Narrow
Scope whole top-level folder + subfolders the <platform>-essential tag (server-side)
Test Type Smoke + Regression any — the tag defines the scope
Case state Active Active
Automation manual only (exclude 10, 23, 24) manual only (exclude 10, 23, 24)

Narrow variants deliberately drop the test-type filter, since a tagged case counts regardless of type, but keep the state and automation-type filters so retired and already-automated cases stay out.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts21d3 checks · Risk SAFE
  • Gen Agent Trust Hub21d

    This skill automates the setup of manual regression test runs in Testmo for Bitwarden software releases. It safely manages test specifications and coordinates with established internal tools without exhibiting any malicious patterns or security vulnerabilities.

  • Socket21d

    No alerts

  • Snyk21d

    Risk: LOW · No issues

Signed by skilld at a11c77b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 weeks ago
What it can do
Reads files
argument-hint
[partial | full] [milestone name]
All 2 allowed tools
ReadSkill(bitwarden-testmo-tools:creating-test-runs)

README badge

README badge for bitwarden/ai-plugins/setting-up-regression-runs