fleet-qa

Plugin fleet-qa from marketplace qa-automation in AndreyKizimenko/qa-automation-poc. Commands read from the repo's manifest — 9 days ago.

Skills (8)

• fleet-bug-file

  File a Fleet bug on GitHub from a finding — verify it reproduces, pin the discovered/reproduced builds, decide released vs unreleased and the product group, write the issue from Fleet's bug-report template with QA's field rules, create it with gh, hand back the screenshots to attach, and record setu

• fleet-bug-qa

  QA a Fleet bug fix or security-report fix end to end against two live instances — a pre-fix one and a fixed one — by first reproducing the problem on the pre-fix instance, then verifying the fix plus regression and halo coverage, with API drivers, osquery-perf hosts, parallel agents and UI screensho

• fleet-bug-retest

  Go through the bugs in the user's filed-bugs tracker (filed-bugs/INDEX.md in their QA workspace — the bugs they filed with fleet-bug-file), find which ones now have a fix merged into a build running on their instances, and re-verify those — replaying the recorded checks on the pre-fix and fixed inst

• fleet-explore

  Run a chartered exploratory-testing session on a live Fleet instance — Claude explores one feature, page or area with worst-case data, every entry point and scope, lifecycle and interruption tours, keeps a timestamped tagged log, and ends with a debrief (what was covered and what wasn't, a decision

• fleet-loadtest-qa

  QA and investigate Fleet behavior at scale on a load test (the 100k-host osquery-perf "loadtest" environments in AWS) — reproduce a scale or performance bug, verify its fix before and after an upgrade, find what breaks when reports, policies, scripts and automations are stacked, recover a load test

• fleet-quickwin-qa

  QA a small Fleet change end to end on the current RC instance, with Claude driving — typically a `quick-win` / `~context` issue, a copy or help-text change, a new API field or parameter, a small UI tweak, a fleetctl flag. Reads the issue and PR, confirms the change is in the build (and whether it al

• fleet-story-qa

  Partner with the QA engineer on a Fleet user story (label `story`) — read the story, its test plan and every PR, map the diff to what's risky, check the plan is current (fleet-test-plan writes it) and flag stale rows, then split the work — Claude takes API, fleetctl, GitOps, role matrices, obvious U

• fleet-test-plan

  Write or update the test plan for a Fleet user story (label `story`). Runs first from the finalized design (story, API/YAML docs PRs, Figma, linked docs, the code it will touch, past bugs in the area), then again once the engineer's PR is up, folding in what the diff shows. Produces the story's "Tes