bitwarden-testing-tools

Plugin bitwarden-testing-tools from marketplace bitwarden-marketplace in bitwarden/ai-plugins. Commands read from the repo's manifest — 6 days ago.

Skills (6)

• assessing-requirement-readiness

  Use when the question is whether a Jira story is READY to build and test, not what the story is about. Judges acceptance criteria for clarity, testability, and completeness and returns a go/no-go verdict with the specific gaps. Triggers on "is this ticket ready to build", "can I start work on PM-123

• assessing-test-coverage

  Use when determining what test coverage ALREADY exists for a specific change (a PR, Jira key, Tech Breakdown doc, Testmo CSV, changed paths, or named component), or which existing Testmo cases and tests it makes obsolete, wrong, or duplicated, including other teams' cases. Use it before writing new

• designing-test-plans

  Use when designing the tests a READY Jira story or epic needs, derived from its acceptance criteria, with traceability from each criterion to its tests. Triggers on "design the tests for PM-123", "build a test plan for this epic", "what tests do these acceptance criteria need", "map tests to the acc

• recommending-test-layers

  Use when deciding WHICH new tests a change needs and at WHICH layer each belongs, working from a Jira key, a Testmo CSV, an assessing-test-coverage report, a PR, or a feature description. Triggers on "should I add integration tests here", "are unit tests enough", "what tests should I add and where",

• setting-up-regression-runs

  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

• writing-manual-test-cases

  Use when authoring NEW manual test cases in Gherkin format from a feature description, Jira ticket, acceptance criteria, PR, or design doc — the kind a QA engineer imports into Testmo. Triggers on "write test cases for", "manual test cases", "Gherkin scenarios for this ticket", "test cases for Testm

MCP servers (1)

• bitwarden-test-automation

  runs: bash -c cd "${CLAUDE_PLUGIN_ROOT}/mcp/bitwarden-test-automation-mcp-server" && CPV=$(node -p 'require("./package.json").devDependencies.corepack.trim()') && npm exec --yes corepack@"$CPV" -- pnpm inst

Similar plugins