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

/creating-test-runs

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

Create test runs in Bitwarden's Testmo instance from reviewable JSON filter specs. Use when asked to create one or more Testmo runs, link runs to a Testmo milestone, select cases for a run, or write or debug a run filter spec built from folder/tag/test-type/team/automation filters. Accepts several specs in one pass. Dry-run first; writes mutate the live instance. For a release's QA manual regression suite, use bitwarden-testing-tools' setting-up-regression-runs instead — it owns the release profiles and specs and delegates here.

Use this Skill: https://skilld.dev/gh/bitwarden/ai-plugins/creating-test-runs

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

referencesmulti-configuration-runs.md

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

Multi-configuration runs

Read this before creating or reviewing any spec that carries a config_id. These runs need a manual Testmo UI pass after the script finishes, and the pass is mandatory.

Some platforms ship several same-named runs distinguished only by Testmo Configuration (for example one Mobile run per OS). Each variant is its own spec file with the same run_name and a different config_id. Look config ids up via GET /projects/{id}/configs.

Testmo's /cases API cannot filter by configuration and exposes no per-case config assignment, so these are always two-step runs:

  1. Step 1 (the script): create the run with the spec's case set and config_id.
  2. Step 2 (manual, Testmo UI): remove the cases that belong to the other configurations. Each spec documents its own step 2 in _comment.

Until step 2 is done the run holds the wrong case set. The script lists every affected run under MANUAL STEP 2 REQUIRED; pass that list on to the user.

A common split is broad + narrow: one variant covers a whole folder, and the others are driven by a tag that marks the essential cases. A narrow, tag-only spec has no folder or test-type filter behind it, so verify the tag against GET /projects/{id}/tags before trusting it — a wrong or duplicated tag name yields the wrong case set rather than an error.

"config_id": null is a deliberate placeholder meaning "this run needs a Configuration that has not been looked up yet." Dry-runs still work so case counts can be validated, but --create refuses, since the variants would be indistinguishable.

Source: SKILL.md on GitHub

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.

1 warning21d3 checks · Risk SAFE
  • Gen Agent Trust Hub21d

    This skill provides a secure way to create test runs in Bitwarden's Testmo instance using JSON filter specifications. It demonstrates high security maturity by implementing protections against credential exposure in process lists, validating project IDs to prevent path traversal, and enforcing a mandatory human-in-the-loop review process before performing any API write operations.

  • Socket21d

    No alerts

  • Snyk21d

    Risk: MEDIUM · 1 issue

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

README badge

README badge for bitwarden/ai-plugins/creating-test-runs