test-instructions

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Test Instructions

测试说明

Emit a checklist the operator can copy-paste to verify the work.
生成一份操作员可直接复制粘贴以验证工作成果的检查清单。

Process

流程

  1. Identify the worktree. Absolute path via
    git rev-parse --show-toplevel
    .
  2. Skim the diff.
    git diff --stat <base>
    (base resolved via
    references/build-tool-detection.md#base_branch
    ) to know which areas were touched. No deep file reads.
  3. Identify the ticket via
    references/issue-tracker-detection.md
    . Skip if none.
  4. Pick test commands from
    .turkit.yaml → commands.test
    /
    commands.check
    , or the project's build-tool defaults.
  5. Emit the block below using
    references/output-preferences.md
    for operator-facing language/style. No prose around it.
  1. 确定工作目录:通过
    git rev-parse --show-toplevel
    获取绝对路径。
  2. 浏览差异:执行
    git diff --stat <base>
    (基准分支通过
    references/build-tool-detection.md#base_branch
    确定),了解改动涉及的区域。无需深入阅读文件内容。
  3. 识别工单:通过
    references/issue-tracker-detection.md
    识别工单。若无工单则跳过此步骤。
  4. 选择测试命令:从
    .turkit.yaml → commands.test
    /
    commands.check
    中选择,或使用项目构建工具的默认命令。
  5. 生成下方内容块:遵循
    references/output-preferences.md
    中面向操作员的语言风格要求。无需额外说明性文字。

Output template

输出模板

Test Instructions — <TICKET-ID> <short title>

Worktree:
```bash
cd <absolute-worktree-path>
```
测试说明 — <工单ID> <简短标题>

工作目录:
```bash
cd <绝对工作目录路径>
```

1. Automated

1. 自动化测试

bash
<test/check commands, copy-pasteable, no placeholders>
bash
<可直接复制粘贴的测试/检查命令,无占位符>

2. Live (omit if no runtime to exercise)

2. 实时测试(若无运行时可验证则省略)

bash
<server start command with env vars if needed>
Then:
  • <UI step or curl one-liner> → <expected result>
bash
<启动服务器的命令,如需环境变量请一并包含>
然后:
  • <UI操作步骤或curl单行命令> → <预期结果>

3. Edge cases

3. 边缘案例

  • <happy path — one line>
  • <critical edge case>
  • <likely adjacent regression>
  • <正常流程 — 单行描述>
  • <关键边缘案例>
  • <可能的相邻回归问题>

Résumé

总结

<2–3 sentences: what changed, expected behaviour, what to pay attention to during the test>
undefined
<2–3句话:说明改动内容、预期行为以及测试过程中需要注意的事项>
undefined

Rules

规则

  • Commands must run as-is. No
    <placeholder>
    except secrets the operator must fill.
  • Max ~3 items in Edge cases. Happy path + 1–2 critical edges. If more, you're over-testing.
  • Omit "Live" if there's no runtime to exercise (pure refactor, types-only change, docs).
  • No "Prerequisites" section, no "Expected result" subsections — fold into the line.
  • Apply
    references/output-preferences.md
    for operator-facing language/style. Translate
    Résumé
    naturally when the configured language is not French.
  • 命令必须可直接运行:除操作员需填写的密钥外,不得包含
    <占位符>
    。
  • 边缘案例最多约3项:包含正常流程 + 1–2个关键边缘案例。若超过此数量,则属于过度测试。
  • 省略“实时测试”部分:当无运行时可验证时(如纯重构、仅类型变更、文档修改),无需此部分。
  • 不得包含“前置条件”章节或“预期结果”子章节 — 相关内容需整合到对应行中。
  • 面向操作员的语言风格需遵循
    references/output-preferences.md
    。当配置语言为非法语时,需将
    Résumé
    自然翻译为对应语言(中文环境下为“总结”)。