返回提示词目录第 1178 页

软件发布前集中找错活动策划

围绕发布范围安排探索测试、人员分工与缺陷分级,产出活动流程及发布决策依据。

完整提示词

<context>
You plan a bug bash: a time-boxed session where many people explore a release to find problems before users do. Bug bashes waste time when everyone tests the same happy path, the environment or test accounts break in the first ten minutes, reports are duplicated and too vague to reproduce, severity is argued instead of defined, and nobody decides what the findings mean for the release. Good ones use short exploratory charters, mix engineers with people who think like customers, and end with a clear go, go-with-fixes or no-go input.

Participants: {{participants}}
Session length: {{duration_minutes}} minutes
</context>

<task>
<release_scope>
{{release_scope}}
</release_scope>

1. Set the goal and exit criteria: what this bash must give confidence in, and the rule for the release input (for example no open blocker or critical, majors each with an owner and decision).
2. Write five to ten charters in the form "Explore <area> with <resources or persona> to discover <kind of risk>", weighted to risky and changed areas, covering platforms, accessibility, slow networks, permissions and roles, edge data (empty, huge, unicode, time zones), upgrade from the previous version, and error paths.
3. Assign participants to charters, pairing a non-engineer with an engineer where possible, and rotate halfway for fresh eyes on the riskiest areas.
4. Setup checklist, done the day before: the build and environment frozen and smoke-tested, test accounts per role, seeded data, feature flags set, devices or browsers listed, where to file bugs, and a tagged label for this bash.
5. Bug template: title as "area: what fails when", steps, expected, actual, environment and build, account used, screenshot or recording, and suspected severity.
6. Severity rules with examples from this release: blocker (data loss, security, payment or core flow broken for many), critical, major, minor, cosmetic. The triager decides, not the reporter.
7. Session run sheet in minutes: kickoff (about 10 minutes: goal, charters, how to report), testing with a mid-point rotation, live triage by one or two people deduplicating and assigning severity as bugs arrive, and a wrap-up with the top findings.
8. After the bash: triage meeting within a day, fix-or-defer decisions per major and above with owners, a short summary with counts by severity and area, the release input, and charters to automate as regression tests.
</task>

<constraints>
- Use only the scope given; if the release date, platforms or risky areas are missing, list them as questions and mark [X] where they matter.
- Keep each charter achievable within the session; no "test everything".
- Never use real customer data or production accounts; require test data.
- Keep the tone inclusive for non-engineers: no assumed tools knowledge beyond the bug form.
</constraints>

<output_format>
## Goal and exit criteria
Two to four bullets.

## Charters
Table: charter | area | risk targeted | suggested participants.

## Participants and pairing
Bullets, with the rotation.

## Setup checklist
Checklist with owner placeholders.

## Bug template
The template in a code block.

## Severity rules
Table: severity | definition | example from this release | release impact.

## Session run sheet
Table: minute | activity | who.

## After the bash
Numbered follow-up steps.
</output_format>

可替换内容

  • {{participants}}
  • {{duration_minutes}}
  • {{release_scope}}
  • [X]

分类与标签

编程开发、探索测试、发布验收、缺陷分级、测试活动策划

前往 AI 图片创作