Desktop QA Flows
Testing & Qualitydesktop-qa-flowsDesktop QA Flows is an Agent Skill for testing & quality published in the RocketChat/Rocket.Chat.Electron repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Create or review Qase-ready QA flows for Rocket.Chat Desktop PRs and branches.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/RocketChat/Rocket.Chat.Electron/blob/HEAD/skills/desktop-qa-flows/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/desktop-qa-flows, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Desktop QA Flows
Use this skill when asked to create, review, or improve QA flows for a Rocket.Chat Desktop PR, branch, release candidate, or changed feature.
Canonical References
Read these before authoring flows:
AGENTS.mdqa/AGENTS.mdqa/README.mdqa/flow-template.md
Those files define the schema and validation rules. This skill defines the repeatable PR workflow.
Workflow
- Lock the comparison range: base branch, head branch or commit, and whether the requested range is fully in scope.
- Inspect the changed implementation before writing steps: changed files, commits, tests, React components, Fuselage icons, i18n labels, menu definitions, modal buttons, platform guards, docs, installers, and helper pages.
- Map changed Desktop surfaces to user-visible risk:
- Electron main process, preload, IPC, and deep links.
- Settings UI, menus, modals, server list, i18n, and layout.
- OS protocol handlers, default apps, registry, desktop files, and cold launch behavior.
- Packaging, installers, release policy, startup, persistence, shortcuts, workspace routing, and diagnostics.
- Compare those risks with existing
qa/**/flows/*.md. - Update an existing flow when it already covers the same user-visible hypothesis.
- Add a new flow when the changed surface creates a new user-visible risk.
- Create a new
qa/<feature-slug>/pack when the risk does not belong in an existing pack. - Write every branch-derived flow with
## Review Basis: comparison range, changed surface, user-visible risk, hypothesis, and smallest useful proof. - Keep every step visually findable. Put screen region, relative position, icon
shape, nearby UI, visible labels, and confirmation state directly in the
Actioncell. - Add static helper HTML or read-only scripts when they reduce ambiguity for clickable links, protocol handlers, OS checks, or repeated evidence capture.
Coverage Rules
- Do not claim full QA unless the full requested comparison range was checked.
- Mark unchanged or already-covered surfaces explicitly in the summary.
- Classify result findings as
confirmed,suspected, orblocked. - If runtime validation is not practical, use the smallest useful proof: an existing test, targeted test, local UI repro, OS-level repro, or code-path proof.
- Keep Qase source IDs in the repo and leave generated Qase IDs empty until a case already exists in Qase.
Validation
After changing QA packs, run:
node qa/scripts/validate-flows.mjs qa/<pack>
node qa/scripts/export-qase-csv.mjs qa/<pack>
git diff --check
Report any unvalidated pack or partial surface review clearly.