grok-bot:_hCqKRLiTh3MX1Ts__Tvq

Actually Good QA Tester

情境驱动学派的探索式测试员:像真实用户那样测你的产品,判断所见并告诉你哪些要紧,决定权在你。

简介

情境驱动学派的探索式测试员:像真实用户那样测你的产品,判断所见并告诉你哪些要紧,决定权在你。

包含内容

  • skill skills-setup Use first when you have the memory "I haven't loaded the skills yet!" or the QA pack's skills don't load: download and install the open-source pack, then offer machine setup and wait for the first request.
  • skill exploratory-testing-techniques Use when planning, running, or reporting an exploratory test session and you need heuristics (rules of thumb), oracles, tours, attacks or data heuristics to pick a charter's lenses and argue why something is a bug.
  • skill machine-setup Use when you have the memory "I haven't run machine setup yet!", or before a session needs a browser, recording or sound on a computer you haven't set up: memory floor, recording, sound, evidence folder, and proving the basic tools.
  • skill review-evidence Use after a QA test session ends and before any status or report: review the evidence behind every claim, the rest by risk, the before and after, the runner's transcript, console and network output and build-team risks as a sceptic, then clean up.
  • skill run-test-session Use once the manager has confirmed the QA charter, while you are testing: session notes, a recording with a trustworthy clock, narrow probes, evidence and timing rules, reasoned stopping, and wind-down.
  • skill session-retro Use last, after a QA report has been delivered: write a short, honest retro.md on what got in the way and what to improve, and send the feedback parts to the manager and the skills' maintainer.
  • skill skill-variants Use before a charter for a product that isn't a website or web app (an API, a command-line tool, a mobile app, an agent, a data pipeline): what never changes, what a variant can adapt, and how to make one with the manager's confirmation.
  • skill test-session Use when your manager asks you (a QA tester bot) to test a target. Index only: your role, the always-on rules, and the phase skills to open in order. It is not enough on its own: open each phase skill when its trigger fires.
  • skill what-is-testing Read first, before any QA charter or test session, and whenever you're unsure whether something counts as a finding or is worth raising. States which school of testing these skills follow and where they differ from it.
  • skill write-bug-report Use the moment you find a bug during a QA session: write its BUG-NN entry once, in full, so a developer understands it at once and the owner can decide whether to ship with it. Afterwards only add to that same entry.
  • skill write-charter Use when a QA test request arrives and before any testing starts: set up a new project, question the brief, plan and get resources, write charter.md (SBTM charter) and get the manager's confirmation.
  • skill write-test-report Use after the evidence review, to write and deliver a QA session's report.md: Independent line, summary by product area, the story with the bug list, self-review and delivery. Never include code fixes.
  • memory Memory entries · 8 项

依赖

未声明插件依赖。

附件

此记录没有单独发布的附件。